Frequency division multiplexing for mixed numerology

ABSTRACT

A base station may utilize frequency division multiplexing (FDM) techniques to signal synchronization signal (SS) blocks and downlink transmissions (e.g., data/control transmissions). The base station may configure a configuration for a bandwidth part (BWP) of a carrier for downlink transmissions. The BWP configuration may include a transmission attribute (e.g., a subcarrier spacing (SCS)) for downlink transmissions within the BWP. The base station may transmit a grant for a downlink transmission to a user equipment (UE). In some cases, the downlink transmission may be scheduled for a set of resources that overlap in time with a SS block for the carrier. The base station may transmit downlink transmissions within the BWP using transmission attributes configured for the BWP and/or using SS block transmission attributes, depending on capabilities of the UE, on whether the time resources of the downlink transmission that are FDMed with the SS block, etc.

CROSS REFERENCES

The present Application for Patent is a Continuation of U.S. patentapplication Ser. No. 16/184,853 by Akkarakaran et al., entitled“Frequency Division Multiplexing For Mixed Numerology” filed Nov. 8,2018, which claims benefit of U.S. Provisional Patent Application No.62/584,108 by Akkarakaran, et al., entitled “Frequency DivisionMultiplexing For Mixed Numerology,” filed Nov. 9, 2017, assigned to theassignee hereof, and expressly incorporated by reference in itsentirety.

BACKGROUND

The following relates generally to wireless communication, and morespecifically to frequency division multiplexing (FDM) for bandwidth part(BWP) transmissions with mixed attributes.

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include fourth generation (4G) systems such as aLong Term Evolution (LTE) systems or LTE-Advanced (LTE-A) systems, andfifth generation (5G) systems which may be referred to as New Radio (NR)systems. These systems may employ technologies such as code divisionmultiple access (CDMA), time division multiple access (TDMA), frequencydivision multiple access (FDMA), orthogonal frequency division multipleaccess (OFDMA), or discrete Fourier transform-spread-orthogonalfrequency division multiple access (DFT-s-OFDM). A wirelessmultiple-access communications system may include a number of basestations or network access nodes, each simultaneously supportingcommunication for multiple communication devices, which may be otherwiseknown as user equipment (UE).

In some wireless communications systems (e.g., systems supportingmillimeter wave (mmW) communications), beamforming may be used in orderto overcome the relatively high path losses associated with frequenciesin these systems. In order to support beamformed transmissions,communicating wireless devices (e.g., a base station and UE) may beoperable to discover and maintain suitable beams for a givencommunication link via synchronization signals. The synchronizationsignals may be transmitted in synchronization signal (SS) blocks, whichmay also be used, for example, for cell acquisition procedures, celltiming synchronization, etc. Further, in such wireless communicationssystems, connections may be established using a relatively wide channelfrequency bandwidth. In some cases, one or more portions of the channelfrequency bandwidth, referred to as BWPs, may be used for communicationswith a UE. In such cases, if a relatively small amount of data is to betransferred between the UE and a base station, a single BWP may be usedfor a transmission, and if a relatively large amount of data is to betransferred, two or more BWPs may be used for the transmission. In someexamples, such connections may be made according to a carrieraggregation (CA) mode, in which multiple component carriers (CCs), eachof which can have one or more BWPs, may be used together to provide highdata rate communications. Transmission attributes (e.g., subcarrierspacing (SCS), transmission beam direction, etc.) used for transmissionswithin a CC or BWP may differ from transmission attributes used for SSblocks. In cases where transmissions within BWPs and SS blocks are bothto be communicated (e.g., via frequency division multiplexing (FDM)),complexities may arise due to, for example, capabilities of a receivingUE to handle such mixed transmission attributes. Efficient techniquesfor handling mixed transmission attributes associated with SS blocks andtransmissions within BWPs may thus be desired.

SUMMARY

The described techniques relate to improved methods, systems, devices,or apparatuses that support frequency division multiplexing (FDM) forbandwidth part (BWP) transmissions with mixed attributes. Generally, thedescribed techniques provide for efficient handling of mixedtransmission attributes (e.g., subcarrier spacing (SCS), transmissionand/or reception beam directions, etc.) associated with synchronizationsignal (SS) blocks and transmissions within BWPs. A user equipment (UE)may maintain timing synchronization (e.g., symbol timingsynchronization) with a cell by monitoring for SS blocks routinelytransmitted by a base station. In some cases, a base station may utilizeFDM techniques for transmitting SS blocks and downlink transmissions(e.g., physical downlink shared channel (PDSCH), physical downlinkcontrol channel (PDCCH), channel state information reference signal(CSI-RS), etc.).

According to aspects of the present disclosure, a base station mayconfigure a configuration for a BWP of a carrier for downlinktransmissions. The BWP configuration may include a first transmissionattribute (e.g., a BWP SCS, etc.) for downlink transmissions within theBWP. The base station may then transmit a grant for a downlinktransmission to a UE. In some cases, the downlink transmission may bescheduled (e.g., via the grant) for a set of resources that areoverlapping in time with a SS block for the carrier. The downlinktransmission may be associated with transmission attributes such as abeam direction. Where there is overlap in time (e.g., at least a portionof the set of resources are FDMed with the SS block), efficienttechniques for handling transmission attributes associated with SSblocks and transmission attributes associated with transmissions withinBWPs are now described.

In a first example, the set of resources of the downlink transmissionthat overlap with the SS block may be transmitted using a secondtransmission attribute (e.g., the SS block SCS, the SS block beamdirection, etc.). Further, the remainder of the downlink transmission(e.g., the remaining time resources of the downlink transmission notincluding the set of overlapping resources) may be transmitted using thefirst transmission attribute (e.g., a BWP SCS different from the SSblock SCS, a beam direction different from the SS block beam direction,etc.). That is, the downlink transmission FDMed resources may beassociated with SS block transmission attributes during time resourcesthat overlap with the SS block, and the remaining time resources of thedownlink transmission that are not FDMed with the SS block may beassociated with different transmission attributes configured for the BWP(e.g., BWP transmission attributes) or for the transmissions (e.g.,transmissions that don't overlap with SS block). For example, datatransmissions may be associated with a beam direction that is differentthan the SS block beam direction.

In a second example, the entire downlink transmission may be transmittedusing transmission attributes configured for the BWP (e.g., includingportions of the downlink transmission, or time resources of the downlinktransmission, that are FDMed with the SS block).

In a third example, the entire downlink transmission may be transmittedusing SS block transmission attributes (e.g., including portions of thedownlink transmission, or time resources of the downlink transmission,that are FDMed with the SS block).

In some cases, implementation of the techniques described above may beselected based on FDM capabilities of the UE. For example, the basestation may transmit the downlink transmission (using BWP transmissionattributes and/or SS block transmission attributes) based on a receivedcapability message from the UE. The capabilities message may indicatewhether the UE supports FDM, supports FDM with mixed transmissionattributes, supports FDM reception on different beam directions, etc.Further, FDM of downlink transmissions within a configured BWP and a SSblock may only refer to overlap with a SS block intended for the UE.That is, a base station may transmit several SS blocks to other UEswithin the wireless communications system that may occur during the sametime as the downlink transmission, however only SS blocks intended forthe UE that is receiving the downlink transmission (e.g., for which thatUE is expected to receive or monitor) are included when referencing FDM.

A method of wireless communication is described. The method may includeidentifying a configuration for a BWP of a carrier, the configurationcomprising a first value for a transmission attribute for transmissionswithin the BWP, receiving a grant for a downlink transmission, thedownlink transmission scheduled for a set of resources in the BWP thatare overlapping in time with a synchronization signal block for thecarrier, the synchronization signal block being transmitted using asecond value for the transmission attribute, and receiving the downlinktransmission, wherein the receiving comprises applying the second valuefor the transmission attribute for at least a portion of the set ofresources.

An apparatus for wireless communication is described. The apparatus mayinclude means for identifying a configuration for a BWP of a carrier,the configuration comprising a first value for a transmission attributefor transmissions within the BWP, means for receiving a grant for adownlink transmission, the downlink transmission scheduled for a set ofresources in the BWP that are overlapping in time with a synchronizationsignal block for the carrier, the synchronization signal block beingtransmitted using a second value for the transmission attribute, andmeans for receiving the downlink transmission, wherein the receivingcomprises applying the second value for the transmission attribute forat least a portion of the set of resources.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor, and instructions stored in the memory. The instructions maybe operable to cause the processor to identify a configuration for a BWPof a carrier, the configuration comprising a first value for atransmission attribute for transmissions within the BWP, receive a grantfor a downlink transmission, the downlink transmission scheduled for aset of resources in the BWP that are overlapping in time with asynchronization signal block for the carrier, the synchronization signalblock being transmitted using a second value for the transmissionattribute, and receive the downlink transmission, wherein the receivingcomprises applying the second value for the transmission attribute forat least a portion of the set of resources.

A non-transitory computer-readable medium for wireless communication isdescribed. The non-transitory computer-readable medium may includeinstructions operable to cause a processor to identify a configurationfor a BWP of a carrier, the configuration comprising a first value for atransmission attribute for transmissions within the BWP, receive a grantfor a downlink transmission, the downlink transmission scheduled for aset of resources in the BWP that are overlapping in time with asynchronization signal block for the carrier, the synchronization signalblock being transmitted using a second value for the transmissionattribute, and receive the downlink transmission, wherein the receivingcomprises applying the second value for the transmission attribute forat least a portion of the set of resources.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the receiving the downlinktransmission comprises: applying the second value for the transmissionattribute for all of the set of resources.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the receiving the downlinktransmission comprises: applying the first value for the transmissionattribute for a first portion of the set of resources not overlapping intime with the synchronization signal block and the second value for thetransmission attribute for a second portion of the set of resourcesoverlapping in time with the synchronization signal block.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the transmission attributecomprises a SCS. In some examples of the method, apparatus, andnon-transitory computer-readable medium described above, the one or moreBWP transmission attribute comprises a transmission beam direction or areception beam direction.

A method of wireless communication is described. The method may includeconfiguring a configuration for a BWP of a carrier, the configurationcomprising a first value for a transmission attribute for transmissionswithin the BWP, transmitting a grant for a first downlink transmissionin the BWP to a first UE, the first downlink transmission scheduled fora first set of resources that are overlapping in time with asynchronization signal block for the carrier, the synchronization signalblock being transmitted using a second value for the transmissionattribute, and transmitting the first downlink transmission, wherein thetransmitting comprises applying the second value for the transmissionattribute for at least a portion of the first set of resources.

An apparatus for wireless communication is described. The apparatus mayinclude means for configuring a configuration for a BWP of a carrier,the configuration comprising a first value for a transmission attributefor transmissions within the BWP, means for transmitting a grant for afirst downlink transmission in the BWP to a first UE, the first downlinktransmission scheduled for a first set of resources that are overlappingin time with a synchronization signal block for the carrier, thesynchronization signal block being transmitted using a second value forthe transmission attribute, and means for transmitting the firstdownlink transmission, wherein the transmitting comprises applying thesecond value for the transmission attribute for at least a portion ofthe first set of resources.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor, and instructions stored in the memory. The instructions maybe operable to cause the processor to configure a configuration for aBWP of a carrier, the configuration comprising a first value for atransmission attribute for transmissions within the BWP, transmit agrant for a first downlink transmission in the BWP to a first UE, thefirst downlink transmission scheduled for a first set of resources thatare overlapping in time with a synchronization signal block for thecarrier, the synchronization signal block being transmitted using asecond value for the transmission attribute, and transmit the firstdownlink transmission, wherein the transmitting comprises applying thesecond value for the transmission attribute for at least a portion ofthe first set of resources.

A non-transitory computer-readable medium for wireless communication isdescribed. The non-transitory computer-readable medium may includeinstructions operable to cause a processor to configure a configurationfor a BWP of a carrier, the configuration comprising a first value for atransmission attribute for transmissions within the BWP, transmit agrant for a first downlink transmission in the BWP to a first UE, thefirst downlink transmission scheduled for a first set of resources thatare overlapping in time with a synchronization signal block for thecarrier, the synchronization signal block being transmitted using asecond value for the transmission attribute, and transmit the firstdownlink transmission, wherein the transmitting comprises applying thesecond value for the transmission attribute for at least a portion ofthe first set of resources.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the transmitting the firstdownlink transmission comprises: applying the second value for thetransmission attribute for all of the first set of resources.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting a second downlinktransmission to a second UE, the second downlink transmissionoverlapping in time with the first downlink transmission and notoverlapping in time with the synchronization signal block, wherein thetransmitting the second downlink transmission comprises inserting aguard band in the frequency domain between the first downlinktransmission and the second downlink transmission.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the transmitting the firstdownlink transmission comprises: applying the first value for thetransmission attribute for a first portion of the first set of resourcesnot overlapping in time with the synchronization signal block and thesecond value for the transmission attribute for a second portion of thefirst set of resources overlapping in time with the synchronizationsignal block.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the transmission attributecomprises a SCS. In some examples of the method, apparatus, andnon-transitory computer-readable medium described above, the one or moreBWP transmission attribute comprises a transmission beam direction or areception beam direction.

A method of wireless communication is described. The method may includeconfiguring a configuration for a BWP of a carrier, the configurationcomprising a first value for a transmission attribute for transmissionswithin the BWP, transmitting a grant for a first downlink transmissionin the BWP to a first UE, the first downlink transmission scheduled fora first set of resources that are overlapping in time with asynchronization signal block for the carrier, the synchronization signalblock being transmitted using a second value for the transmissionattribute, and transmitting the first downlink transmission, wherein thetransmitting comprises applying the first value for the transmissionattribute for the first set of resources and inserting a guard band inthe frequency domain between the first downlink transmission and thesynchronization signal block.

An apparatus for wireless communication is described. The apparatus mayinclude means for configuring a configuration for a BWP of a carrier,the configuration comprising a first value for a transmission attributefor transmissions within the BWP, means for transmitting a grant for afirst downlink transmission in the BWP to a first UE, the first downlinktransmission scheduled for a first set of resources that are overlappingin time with a synchronization signal block for the carrier, thesynchronization signal block being transmitted using a second value forthe transmission attribute, and means for transmitting the firstdownlink transmission, wherein the transmitting comprises applying thefirst value for the transmission attribute for the first set ofresources and inserting a guard band in the frequency domain between thefirst downlink transmission and the synchronization signal block.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor, and instructions stored in the memory. The instructions maybe operable to cause the processor to configure a configuration for aBWP of a carrier, the configuration comprising a first value for atransmission attribute for transmissions within the BWP, transmit agrant for a first downlink transmission in the BWP to a first UE, thefirst downlink transmission scheduled for a first set of resources thatare overlapping in time with a synchronization signal block for thecarrier, the synchronization signal block being transmitted using asecond value for the transmission attribute, and transmit the firstdownlink transmission, wherein the transmitting comprises applying thefirst value for the transmission attribute for the first set ofresources and inserting a guard band in the frequency domain between thefirst downlink transmission and the synchronization signal block.

A non-transitory computer-readable medium for wireless communication isdescribed. The non-transitory computer-readable medium may includeinstructions operable to cause a processor to configure a configurationfor a BWP of a carrier, the configuration comprising a first value for atransmission attribute for transmissions within the BWP, transmit agrant for a first downlink transmission in the BWP to a first UE, thefirst downlink transmission scheduled for a first set of resources thatare overlapping in time with a synchronization signal block for thecarrier, the synchronization signal block being transmitted using asecond value for the transmission attribute, and transmit the firstdownlink transmission, wherein the transmitting comprises applying thefirst value for the transmission attribute for the first set ofresources and inserting a guard band in the frequency domain between thefirst downlink transmission and the synchronization signal block.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the transmitting the firstdownlink transmission applying the first value for the transmissionattribute for the first set of resources may be based on a receivedcapability message from the first UE indicating support for frequencydivision multiplexing of the first and second values for thetransmission attribute.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the transmission attributecomprises a SCS. In some examples of the method, apparatus, andnon-transitory computer-readable medium described above, the one or moreBWP transmission attribute comprises a transmission beam direction or areception beam direction.

A method of wireless communication at a UE is described. The method mayinclude receiving a synchronization signal block for a carrier, thesynchronization signal block associated with synchronization signalblock transmission attributes, identifying one or more BWP transmissionattributes for transmissions within a BWP of the carrier, and receivinga transmission over the BWP of the carrier based on the synchronizationsignal block transmission attributes and the one or more BWPtransmission attributes, where the transmission may be multiplexed withthe synchronization signal block according to a pattern selected from aplurality of predefined multiplexing schemes comprising a time divisionmultiplexing scheme and a frequency division multiplexing scheme.

An apparatus for wireless communication at a UE is described. Theapparatus may include a processor, memory in electronic communicationwith the processor, and instructions stored in the memory. Theinstructions may be executable by the processor to cause the apparatusto receive a synchronization signal block for a carrier, thesynchronization signal block associated with synchronization signalblock transmission attributes, identify one or more BWP transmissionattributes for transmissions within a BWP of the carrier, and receive atransmission over the BWP of the carrier based on the synchronizationsignal block transmission attributes and the one or more BWPtransmission attributes, where the transmission may be multiplexed withthe synchronization signal block according to a pattern selected from aplurality of predefined multiplexing schemes comprising a time divisionmultiplexing scheme and a frequency division multiplexing scheme.

Another apparatus for wireless communication at a UE is described. Theapparatus may include means for receiving a synchronization signal blockfor a carrier, the synchronization signal block associated withsynchronization signal block transmission attributes, identifying one ormore BWP transmission attributes for transmissions within a BWP of thecarrier, and receiving a transmission over the BWP of the carrier basedon the synchronization signal block transmission attributes and the oneor more BWP transmission attributes, where the transmission may bemultiplexed with the synchronization signal block according to a patternselected from a plurality of predefined multiplexing schemes comprisinga time division multiplexing scheme and a frequency divisionmultiplexing scheme.

A non-transitory computer-readable medium storing code for wirelesscommunication at a UE is described. The code may include instructionsexecutable by a processor to receive a synchronization signal block fora carrier, the synchronization signal block associated withsynchronization signal block transmission attributes, identify one ormore BWP transmission attributes for transmissions within a BWP of thecarrier, and receive a transmission over the BWP of the carrier based onthe synchronization signal block transmission attributes and the one ormore BWP transmission attributes, where the transmission may bemultiplexed with the synchronization signal block according to a patternselected from a plurality of predefined multiplexing schemes comprisinga time division multiplexing scheme and a frequency divisionmultiplexing scheme.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the transmission includes adownlink control channel transmission. In some examples of the method,apparatuses, and non-transitory computer-readable medium describedherein, the transmission includes a downlink shared channeltransmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the synchronization signalblock transmission attributes include a first SCS and the one or moreBWP transmission attributes include a second SCS. In some examples ofthe method, apparatuses, and non-transitory computer-readable mediumdescribed herein, the first SCS and the second SCS may be different.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the one or more BWPtransmission attributes include a transmission beam direction or areception beam direction.

A method of wireless communication is described. The method may includetransmitting, to a UE, a synchronization signal block for a carrier, thesynchronization signal block associated with synchronization signalblock transmission attributes, configuring one or more BWP transmissionattributes for transmissions within a BWP of the carrier, andtransmitting, to the UE, a transmission over the BWP of the carrierbased on the synchronization signal block transmission attributes andthe one or more BWP transmission attributes, where the transmission maybe multiplexed with the synchronization signal block according to apattern selected from a plurality of predefined multiplexing schemescomprising a time division multiplexing scheme and a frequency divisionmultiplexing scheme.

An apparatus for wireless communication is described. The apparatus mayinclude a processor, memory in electronic communication with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to transmit, to aUE, a synchronization signal block for a carrier, the synchronizationsignal block associated with synchronization signal block transmissionattributes, configure one or more BWP transmission attributes fortransmissions within a BWP of the carrier, and transmit, to the UE, atransmission over the BWP of the carrier based on the synchronizationsignal block transmission attributes and the one or more BWPtransmission attributes, where the transmission may be multiplexed withthe synchronization signal block according to a pattern selected from aplurality of predefined multiplexing schemes comprising a time divisionmultiplexing scheme and a frequency division multiplexing scheme.

Another apparatus for wireless communication is described. The apparatusmay include means for transmitting, to a UE, a synchronization signalblock for a carrier, the synchronization signal block associated withsynchronization signal block transmission attributes, configuring one ormore bandwidth BWP transmission attributes for transmissions within aBWP of the carrier, and transmitting, to the UE, a transmission over theBWP of the carrier based on the synchronization signal blocktransmission attributes and the one or more BWP transmission attributes,where the transmission may be multiplexed with the synchronizationsignal block according to a pattern selected from a plurality ofpredefined multiplexing schemes comprising a time division multiplexingscheme and a frequency division multiplexing scheme.

A non-transitory computer-readable medium storing code for wirelesscommunication is described. The code may include instructions executableby a processor to transmit, to a UE, a synchronization signal block fora carrier, the synchronization signal block associated withsynchronization signal block transmission attributes, configure one ormore BWP transmission attributes for transmissions within a BWP of thecarrier, and transmit, to the UE, a transmission over the BWP of thecarrier based on the synchronization signal block transmissionattributes and the one or more BWP transmission attributes, where thetransmission may be multiplexed with the synchronization signal blockaccording to a pattern selected from a plurality of predefinedmultiplexing schemes comprising a time division multiplexing scheme anda frequency division multiplexing scheme.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the transmission includes adownlink control channel transmission. In some examples of the method,apparatuses, and non-transitory computer-readable medium describedherein, the transmission includes a downlink shared channeltransmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting a secondtransmission to a second UE, the second transmission overlapping in timewith the transmission and not overlapping in time with thesynchronization signal block, where the transmitting the secondtransmission may include inserting a guard band in the frequency domainbetween the transmission and the second transmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the synchronization signalblock transmission attributes include a first SCS and the one or moreBWP transmission attributes include a second SCS. In some examples ofthe method, apparatuses, and non-transitory computer-readable mediumdescribed herein, the first SCS and the second SCS may be different.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the one or more BWPtransmission attributes include a transmission beam direction or areception beam direction.

A method of wireless communication is described. The method may includetransmitting, to a UE, a synchronization signal block for a carrier, thesynchronization signal block associated with synchronization signalblock transmission attributes, configuring one or more BWP transmissionattributes for transmissions within a BWP of the carrier, andtransmitting, to the UE, a transmission over the BWP of the carrierbased on the synchronization signal block transmission attributes andthe one or more BWP transmission attributes, where the transmission maybe multiplexed with the synchronization signal block according to apattern selected from a plurality of predefined multiplexing schemescomprising a time division multiplexing scheme and a frequency divisionmultiplexing scheme.

An apparatus for wireless communication is described. The apparatus mayinclude a processor, memory in electronic communication with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to transmit, to aUE, a synchronization signal block for a carrier, the synchronizationsignal block associated with synchronization signal block transmissionattributes, configure one or more BWP transmission attributes fortransmissions within a BWP of the carrier, and transmit, to the UE, adownlink transmission over the BWP of the carrier based on thesynchronization signal block transmission attributes and the one or moreBWP transmission attributes, where the downlink transmission ismultiplexed with the synchronization signal block according to a patternselected from a plurality of predefined multiplexing schemes including atime division multiplexing scheme and a frequency division multiplexingscheme, the pattern including an inserted guard band in the frequencydomain between the downlink transmission and the synchronization signalblock.

Another apparatus for wireless communication is described. The apparatusmay include means for transmitting, to a UE, a synchronization signalblock for a carrier, the synchronization signal block associated withsynchronization signal block transmission attributes, configuring one ormore BWP transmission attributes for transmissions within a BWP of thecarrier, and transmitting, to the UE, a downlink transmission over theBWP of the carrier based on the synchronization signal blocktransmission attributes and the one or more BWP transmission attributes,where the downlink transmission is multiplexed with the synchronizationsignal block according to a pattern selected from a plurality ofpredefined multiplexing schemes including a time division multiplexingscheme and a frequency division multiplexing scheme, the patternincluding an inserted guard band in the frequency domain between thedownlink transmission and the synchronization signal block.

A non-transitory computer-readable medium storing code for wirelesscommunication is described. The code may include instructions executableby a processor to transmit, to a UE, a synchronization signal block fora carrier, the synchronization signal block associated withsynchronization signal block transmission attributes, configure one ormore BWP transmission attributes for transmissions within a BWP of thecarrier, and transmit, to the UE, a downlink transmission over the BWPof the carrier based on the synchronization signal block transmissionattributes and the one or more BWP transmission attributes, where thedownlink transmission is multiplexed with the synchronization signalblock according to a pattern selected from a plurality of predefinedmultiplexing schemes including a time division multiplexing scheme and afrequency division multiplexing scheme, the pattern including aninserted guard band in the frequency domain between the downlinktransmission and the synchronization signal block.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the synchronization signalblock transmission attributes include a first SCS and the one or moreBWP transmission attributes include a second SCS. In some examples ofthe method, apparatuses, and non-transitory computer-readable mediumdescribed herein, the first SCS and the second SCS may be different.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the transmission attributeincludes a transmission beam direction or a reception beam direction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless communications system thatsupports frequency division multiplexing (FDM) for bandwidth part (BWP)transmissions with mixed attributes in accordance with aspects of thepresent disclosure.

FIG. 2 illustrates an example of a wireless communications system thatsupports FDM for BWP transmissions with mixed attributes in accordancewith aspects of the present disclosure.

FIGS. 3A, 3B and 3C illustrate examples of FDM for BWP transmissionswith mixed attributes in accordance with aspects of the presentdisclosure.

FIGS. 4 and 5 show block diagrams of wireless devices that support FDMfor BWP transmissions with mixed attributes in accordance with aspectsof the present disclosure.

FIG. 6 shows a block diagram of a UE communications manager thatsupports FDM for BWP transmissions with mixed attributes in accordancewith aspects of the present disclosure.

FIG. 7 illustrates a diagram of a system including a device thatsupports FDM for BWP transmissions with mixed attributes in accordancewith aspects of the present disclosure.

FIGS. 8 and 9 show block diagrams of wireless devices that support FDMfor BWP transmissions with mixed attributes in accordance with aspectsof the present disclosure.

FIG. 10 shows a block diagram of a base station communications managerthat supports FDM for BWP transmissions with mixed attributes inaccordance with aspects of the present disclosure.

FIG. 11 illustrates a diagram of a system including a device thatsupports FDM for BWP transmissions with mixed attributes in accordancewith aspects of the present disclosure.

FIGS. 12 through 18 show flowcharts illustrating methods for FDM for BWPtransmissions with mixed attributes in accordance with aspects of thepresent disclosure.

DETAILED DESCRIPTION

A base station may configure one or more synchronization signal (SS)blocks for transmission to a user equipment (UE) for cell acquisitionand timing synchronization procedures. For example, the SS blocks mayinclude symbols allocated for a primary SS (PSS), a secondary SS (SSS),and a physical broadcast channel (PBCH). Such SS blocks may be sentaccording to some SS block transmission attributes, such as somepredefined numerology (e.g., a subcarrier spacing (SCS)). For example,SS blocks may be transmitted according to a 15 kHz or 30 kHz SCS foroperating frequencies less than 6 GHz, and 120 kHz or 240 kHz foroperating frequencies greater than 6 GHz. Additionally, a base stationmay utilize one or more portions of the channel frequency bandwidth,referred to as bandwidth parts (BWPs) for other downlink communicationswith the UE (e.g., physical downlink shared channel (PDSCH), physicaldownlink control channel (PDCCH), channel state information referencesignals (CSI-RS), etc.). In some cases, such downlink transmissionswithin these configured BWPs may be associated with differenttransmission attributes (e.g., a SCS of downlink transmissions withinthe BWP may be different than the SS block SCS). For example, SS blocksmay never use a certain SCS (such as 60 kHz) and thus downlinktransmissions in a BWP associated with such an SCS would always have anSCS different from that of the SS blocks.

In some cases, a base station may use frequency division multiplexing(FDM) techniques to convey downlink transmissions and SS blocks. Thebase station may elect to transmit downlink transmissions within the BWPusing transmission attributes configured for the BWP and/or using SSblock transmission attributes depending on a variety of factors. Suchfactors may include capabilities of the UE, whether the instant timeresources of the downlink transmission are FDMed with the SS block(e.g., on whether the particular time resources of the downlinktransmission overlap with time resources of the SS block), etc.Techniques described herein provide for efficient FDM handling ormanagement of SS blocks along with other downlink transmissions.

Aspects of the disclosure are initially described in the context of awireless communications system. Example FDM scenarios employingtechniques for mixed transmission attributes for transmissions within aBWP are then discussed. Aspects of the disclosure are furtherillustrated by and described with reference to apparatus diagrams,system diagrams, and flowcharts that relate to FDM for BWP transmissionswith mixed attributes.

FIG. 1 illustrates an example of a wireless communications system 100that supports FDM for BWP transmissions with mixed attributes inaccordance with aspects of the present disclosure. The wirelesscommunications system 100 includes base stations 105, UEs 115, and acore network 130. In some examples, the wireless communications system100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A)network, or a New Radio (NR) network. In some cases, wirelesscommunications system 100 may support enhanced broadband communications,ultra-reliable (e.g., mission critical) communications, low latencycommunications, or communications with low-cost and low-complexitydevices. UEs 115 may perform cell acquisition procedures andsynchronization procedures with a base station 105 via monitoring for SSblocks. Once a connection is established, one or more BWPs may beconfigured for a communication link 125 between a base station 105 and aUE 115. In some cases, base stations 105 may utilize FDM to convey SSblocks (e.g., for synchronization) as well as downlink transmissionswithin the one or more configured BWPs.

Base stations 105 may wirelessly communicate with UEs 115 via one ormore base station antennas. Each base station 105 may providecommunication coverage for a respective geographic coverage area 110.Communication links 125 shown in wireless communications system 100 mayinclude uplink transmissions from a UE 115 to a base station 105, ordownlink transmissions, from a base station 105 to a UE 115. Controlinformation and data may be multiplexed on an uplink channel or downlinkchannel according to various techniques. Control information and datamay be multiplexed on a downlink channel, for example, using timedivision multiplexing (TDM) techniques, FDM techniques, or hybridTDM-FDM techniques. In some examples, the control informationtransmitted during a transmission time interval (TTI) of a downlinkchannel may be distributed between different control regions in acascaded manner (e.g., between a common control region and one or moreUE-specific control regions).

UEs 115 may be dispersed throughout the wireless communications system100, and each UE 115 may be stationary or mobile. A UE 115 may also bereferred to as a mobile station, a subscriber station, a mobile unit, asubscriber unit, a wireless unit, a remote unit, a mobile device, awireless device, a wireless communications device, a remote device, amobile subscriber station, an access terminal, a mobile terminal, awireless terminal, a remote terminal, a handset, a user agent, a mobileclient, a client, or some other suitable terminology. A UE 115 may alsobe a cellular phone, a personal digital assistant (PDA), a wirelessmodem, a wireless communication device, a handheld device, a tabletcomputer, a laptop computer, a cordless phone, a personal electronicdevice, a handheld device, a personal computer, a wireless local loop(WLL) station, an Internet of things (IoT) device, an Internet ofEverything (IoE) device, a machine type communication (MTC) device, anappliance, an automobile, or the like.

In some cases, a UE 115 may also be able to communicate directly withother UEs (e.g., using a peer-to-peer (P2P) or device-to-device (D2D)protocol). One or more of a group of UEs 115 utilizing D2Dcommunications may be within the coverage area 110 of a cell. Other UEs115 in such a group may be outside the coverage area 110 of a cell, orotherwise unable to receive transmissions from a base station 105. Insome cases, groups of UEs 115 communicating via D2D communications mayutilize a one-to-many (1:M) system in which each UE 115 transmits toevery other UE 115 in the group. In some cases, a base station 105facilitates the scheduling of resources for D2D communications. In othercases, D2D communications are carried out independently of a basestation 105.

Some UEs 115, such as MTC or IoT devices, may be low cost or lowcomplexity devices, and may provide for automated communication betweenmachines, i.e., Machine-to-Machine (M2M) communication. M2M or MTC mayrefer to data communication technologies that allow devices tocommunicate with one another or a base station without humanintervention. For example, M2M or MTC may refer to communications fromdevices that integrate sensors or meters to measure or captureinformation and relay that information to a central server orapplication program that can make use of the information or present theinformation to humans interacting with the program or application. SomeUEs 115 may be designed to collect information or enable automatedbehavior of machines. Examples of applications for MTC devices includesmart metering, inventory monitoring, water level monitoring, equipmentmonitoring, healthcare monitoring, wildlife monitoring, weather andgeological event monitoring, fleet management and tracking, remotesecurity sensing, physical access control, and transaction-basedbusiness charging.

Base stations 105 may communicate with the core network 130 and with oneanother. For example, base stations 105 may interface with the corenetwork 130 through backhaul links 132 (e.g., S1, etc.). Base stations105 may communicate with one another over backhaul links 134 (e.g., X2,etc.) either directly or indirectly (e.g., through core network 130).Base stations 105 may perform radio configuration and scheduling forcommunication with UEs 115, or may operate under the control of a basestation controller (not shown). In some examples, base stations 105 maybe macro cells, small cells, hot spots, or the like. Base stations 105may also be referred to as eNodeBs (eNBs) 105, next generation NodeBs(gNBs) 105, etc.

In some cases, wireless communications system 100 may be a packet-basednetwork that operates according to a layered protocol stack. In the userplane, communications at the bearer or Packet Data Convergence Protocol(PDCP) layer may be IP-based. A Radio Link Control (RLC) layer may insome cases perform packet segmentation and reassembly to communicateover logical channels. A Medium Access Control (MAC) layer may performpriority handling and multiplexing of logical channels into transportchannels. The MAC layer may also use Hybrid Automatic Repeat Request(HARD) to provide retransmission at the MAC layer to improve linkefficiency. In the control plane, the Radio Resource Control (RRC)protocol layer may provide establishment, configuration, and maintenanceof an RRC connection between a UE 115 and a base station 105, or corenetwork 130 supporting radio bearers for user plane data. At thephysical (PHY) layer, transport channels may be mapped to physicalchannels.

Wireless communications system 100 may support operation on multiplecells or carriers, a feature which may be referred to as carrieraggregation (CA) or multi-carrier operation. A carrier may also bereferred to as a component carrier (CC), a layer, a channel, etc. Theterms “carrier,” “component carrier,” and “channel” may be usedinterchangeably herein. A UE 115 may be configured with multipledownlink CCs and one or more uplink CCs for carrier aggregation. Carrieraggregation may be used with both frequency division duplex (FDD) andtime division duplex (TDD) component carriers.

In some cases, wireless communications system 100 may utilize enhancedcomponent carriers (eCCs). An eCC may be characterized by one or morefeatures including: wider bandwidth, shorter symbol duration, shorterTTIs, and modified control channel configuration. In some cases, an eCCmay be associated with a carrier aggregation configuration or a dualconnectivity configuration (e.g., when multiple serving cells have asuboptimal or non-ideal backhaul link). An eCC may also be configuredfor use in unlicensed spectrum or shared spectrum (where more than oneoperator is allowed to use the spectrum). An eCC characterized by widebandwidth may include one or more segments that may be utilized by UEs115 that are not capable of monitoring the whole bandwidth or prefer touse a limited bandwidth (e.g., to conserve power).

In some cases, an eCC may utilize a different symbol duration than otherCCs, which may include use of a reduced symbol duration as compared withsymbol durations of the other CCs. A shorter symbol duration may beassociated with increased SCS. A TTI in an eCC may consist of one ormultiple symbols. In some cases, the TTI duration (that is, the numberof symbols in a TTI) may be variable. In some cases, an eCC may utilizea different symbol duration than other CCs, which may include use of areduced symbol duration as compared with symbol durations of the otherCCs. A shorter symbol duration is associated with increased SCS. Adevice, such as a UE 115 or base station 105, utilizing eCCs maytransmit wideband signals (e.g., 20, 40, 60, 80 MHz, etc.) at reducedsymbol durations (e.g., 16.67 microseconds). A TTI in eCC may consist ofone or multiple symbols. In some cases, the TTI duration (that is, thenumber of symbols in a TTI) may be variable.

A shared radio frequency spectrum band may be utilized in an NR sharedspectrum system. For example, an NR shared spectrum may utilize anycombination of licensed, shared, and unlicensed spectrums, among others.The flexibility of eCC symbol duration and SCS may allow for the use ofeCC across multiple spectrums. In some examples, NR shared spectrum mayincrease spectrum utilization and spectral efficiency, specificallythrough dynamic vertical (e.g., across frequency) and horizontal (e.g.,across time) sharing of resources. When operating in unlicensed radiofrequency spectrum bands, wireless devices such as base stations 105 andUEs 115 may employ listen-before-talk (LBT) procedures to ensure thechannel is clear before transmitting data. In some cases, operations inunlicensed bands may be based on a CA configuration in conjunction withCCs operating in a licensed band. Operations in unlicensed spectrum mayinclude downlink transmissions, uplink transmissions, or both. Duplexingin unlicensed spectrum may be based on FDD, TDD, or a combination ofboth.

Wireless communications system 100 may operate in an ultra-highfrequency (UHF) region using frequency bands from 300 MHz to 3 GHz. Thisregion may also be known as the decimeter band, since the wavelengthsrange from approximately one decimeter to one meter in length. UHF wavesmay propagate mainly by line of sight, and may be blocked by buildingsand environmental features. However, the waves may penetrate wallssufficiently to provide service to UEs 115 located indoors. Transmissionof UHF waves is characterized by smaller antennas and shorter range(e.g., less than 100 km) compared to transmission using the smallerfrequencies (and longer waves) of the high frequency (HF) or very highfrequency (VHF) portion of the spectrum. Wireless communications system100 may also operate in a super high frequency (SHF) region usingfrequency bands from 3 GHz to 30 GHz, otherwise known as the centimeterband. In some cases, wireless communication system 100 may also utilizeextremely high frequency (EHF) portions of the spectrum (e.g., from 30GHz to 300 GHz), also known as the millimeter band. Systems that usethis region may be referred to as millimeter wave (mmW) systems. Thus,EHF antennas may be even smaller and more closely spaced than UHFantennas. In some cases, this may facilitate use of antenna arrayswithin a UE 115 (e.g., for directional beamforming). However, EHFtransmissions may be subject to even greater atmospheric attenuation andshorter range than UHF transmissions. Techniques disclosed herein may beemployed across transmissions that use one or more different frequencyregions.

Wireless communications system 100 may support millimeter wave (mmW)communications between UEs 115 and base stations 105. Devices operatingin mmW, SHF, or EHF bands may have multiple antennas to allowbeamforming. Beamforming may also be employed outside of these frequencybands (e.g., in any scenario in which increased cellular coverage isdesired). That is, a base station 105 may use multiple antennas orantenna arrays to conduct beamforming operations for directionalcommunications with a UE 115. Beamforming (which may also be referred toas spatial filtering or directional transmission) is a signal processingtechnique that may be used at a transmitter (e.g., a base station 105)to shape and/or steer an overall antenna beam in the direction of atarget receiver (e.g., a UE 115). This may be achieved by combiningelements in an antenna array in such a way that transmitted signals atparticular angles experience constructive interference while othersexperience destructive interference. For example, base station 105 mayhave an antenna array with a number of rows and columns of antenna portsthat the base station 105 may use for beamforming in its communicationwith UE 115. Signals may be transmitted multiple times in differentdirections (e.g., each transmission may be beamformed differently). AmmW receiver (e.g., a UE 115) may try multiple beams (e.g., antennasubarrays) while receiving the signals. Each of these beams may bereferred to as a receive beam in aspects of the present disclosure.

Multiple-input multiple-output (MIMO) wireless systems use atransmission scheme between a transmitter (e.g., a base station 105) anda receiver (e.g., a UE 115), where both transmitter and receiver areequipped with multiple antennas. In some cases, the antennas of a basestation 105 or UE 115 may be located within one or more antenna arrays,which may support beamforming or MIMO operation. One or more basestation antennas or antenna arrays may be collocated at an antennaassembly, such as an antenna tower. In some cases, antennas or antennaarrays associated with a base station 105 may be located in diversegeographic locations. A base station 105 may use multiple antennas orantenna arrays to conduct beamforming operations for directionalcommunications with a UE 115.

Synchronization (e.g., cell acquisition) may be performed usingsynchronization signals or channels transmitted by a network entity(e.g., a base station 105). A base station may transmit SS blockscontaining discovery reference signals. SS blocks may include a PSS, aSSS, and/or a PBCH. A UE 115 attempting to access a wireless network mayperform an initial cell search by detecting a PSS from a base station105. The PSS may enable synchronization of symbol timing and mayindicate a physical layer identity value. The PSS may be utilized toacquire timing and frequency as well as a physical layer identifier. TheUE 115 may then receive an SSS from the base station 105. The SSS mayenable radio frame synchronization and may provide a cell group identityvalue. The cell group identity value may be combined with the physicallayer identifier to form the physical cell identifier (PCID), whichidentifies the cell. The SSS may also enable detection of a duplexingmode and a cyclic prefix (CP) length. The SSS may be used to acquireother system information (e.g., subframe index). The PBCH may be used toacquire additional system information needed for acquisition (e.g.,bandwidth, frame index, etc.). For example, the PBCH may carry a masterinformation block (MIB) and one or more system information blocks (SIBS)for a given cell.

In deployments that use mmW transmission frequencies (e.g., in NR),multiple SS blocks may be transmitted in different directions using beamsweeping in a SS burst and SS bursts may be periodically transmittedaccording to a SS burst set. The duration of an SS burst may be referredto herein as an SS burst set measurement window. The number ofdirections in which the SS blocks are sent during a SS burst (e.g.,during an SS burst set measurement window of 4 or 5 ms) may be differentin different configurations, and the number of directions may also be afunction of the bandwidth over which the base station 105 is operating.For example, SS blocks may be sent (e.g., beamformed) in four differentdirections when the base station 105 is operating in the 0 to 3 GHzrange, in eight different directions when the base station is operatingin the 3 to 6 GHz range, and up to sixty-four different directions whenthe base station is operating at frequencies greater than 6 GHz.

Time intervals in LTE or NR may be expressed in multiples of a basictime unit (which may be a sampling period of T_(s)= 1/30,720,000seconds). Time resources may be organized according to radio frames oflength of 10 ms (T_(f)=307200 T_(s)), which may be identified by asystem frame number (SFN) ranging from 0 to 1023. Each frame may includeten 1 ms subframes numbered from 0 to 9. A subframe may be furtherdivided into two 0.5 ms slots, each of which contains 6 or 7 modulationsymbol periods (depending on the length of the cyclic prefix prependedto each symbol). Excluding the cyclic prefix, each symbol contains 2048sample periods. In NR, the symbol spacing in the time domain may varywith the tone spacing (or SCS) in the frequency domain. For example, anSCS of 240 kHz may correspond to a symbol duration of ˜4 μs, while anSCS of 30 kHz may correspond to a symbol duration of ˜33 μs. In somecases the subframe may be the smallest scheduling unit, also known as aTTI. In other cases, a TTI may be shorter than a subframe or may bedynamically selected (e.g., in short TTI bursts or in selected componentcarriers using short TTIs).

A resource element may consist of one symbol period and one subcarrier(e.g., a 15 kHz frequency range). A resource block may contain 12consecutive subcarriers in the frequency domain and, for a normal cyclicprefix in each orthogonal frequency division multiplexed (OFDM) symbol,7 consecutive OFDM symbols in the time domain (1 slot), or 84 resourceelements. The number of bits carried by each resource element may dependon the modulation scheme (the configuration of symbols that may beselected during each symbol period). Thus, the more resource blocks thata UE receives and the higher the modulation scheme, the higher the datarate may be.

As indicated above, in some cases, multiple BWPs may be configured for acommunication link 125 between a base station 105 and a UE 115. A basestation 105 may provide an indication of an activated BWP to a UE 115through a downlink control information (DCI) transmission that may ormay not include a grant of resources of the BWP. In some cases, the UE115 may establish the connection with the base station 105 in which oneor more CCs may be configured with one or more BWPs and a CC may beactivated through activation of one or more BWPs configured for the CC.Such a CC may be deactivated through deactivation of each BWP configuredfor the CC.

In some cases, SS blocks and downlink transmissions within configuredBWPs employed by wireless communications system 100 may be associatedwith mixed transmission attributes (e.g., a SCS, a beam direction,etc.). That is, different (e.g., mixed) transmission attributes may beassociated with SS block transmissions and other downlink transmissionswithin the BWPs (e.g., control transmissions such as PDCCH, or datatransmissions such as PDSCH, CSI-RS, etc.). Techniques for handling suchmixed transmission attributed (e.g., in FDM scenarios) are discussed inmore detail with reference to the following figures.

FIG. 2 illustrates an example of a wireless communications system 200that supports FDM for BWP transmissions with mixed attributes inaccordance with aspects of the present disclosure. In some examples,wireless communications system 200 may implement aspects of wirelesscommunication system 100. For example, wireless communications system200 includes a base station 105-a and a UE 115-a, each of which may bean example of the corresponding device described with reference toFIG. 1. In the present example, base station 105-a may convey downlinkcommunications 215 via one or more transmit beams 205. UE 115-a mayreceive such communications via one or more receive beams 210. Downlinkcommunications 215 may include one or more SS blocks 225, as well asdownlink transmissions 220 (e.g., downlink data or downlink signals suchas PDSCH, PDCCH, CSI-RS, etc. within a configured BWP). In some cases,downlink communications 215 may employ FDM. Further SS blocks 225 anddownlink transmissions 220 may each be associated with some transmissionattributes (e.g., SCS, a beam direction associated with a transmit beam205, a beam direction associated with a receive beam 210, etc.). In somecases, transmit or receive beam direction may correspond to a beamidentifier (ID).

A base station 105-a may configure one or more SS blocks 225 fortransmission to UE 115-a for cell acquisition and timing synchronizationprocedures (e.g., to assist a UE 115-a in synchronizing with a cellassociated with the base station 105-a). For example, an SS block 225may include signals (e.g., a PSS, a SSS, and PBCH) that assist the UE115-a to acquire the cell's timing. In some cases, base station 115-amay transmit multiple SS blocks 225, for example, in a SS burst thatlasts for a particular duration of time. SS blocks may be transmitted atdifferent times and in different directions using beamforming, forexample, in a beam sweeping pattern (e.g., the beam sweeping patternincluding transmit beams 205-a, 205-b, 205-c, 205-d, etc.). However,such SS bursts may be intended for multiple UEs 115 (e.g., whereas aparticular SS block 225 associated with transmit beam 205-c may beintended for UE 115-a, as further described with reference to FIG. 3).In some examples, SS bursts or SS blocks 225 may be conveyedperiodically such that a UE 115 may maintain synchronization with a basestation 105 over time.

In one example, UE 115-a may form receive beams 210-a and 210-b. In somecases, the receive beams 210-a and 210-b may each receive signals sentover one or more transmit beams 205. Because the signal transmitted overone transmit beam 205 may experience different path losses and phaseshifts on its way to the respective antennas of the UE 115-a, andbecause each receive beam 210-a and 210-b may weight antennas of the UE115-a differently, the signal received over one receive beam 210 mayhave different signal properties from the signal received over adifferent receive beam 210. UE 115-a may select a transmit beam 205 anda receive beam 210 based on the received signal quality. The transmitbeam 205 and corresponding receive beam 210 may be referred to as a beampair. For example, in some cases base station 105-a may repeattransmissions over multiple transmit beams 205 (e.g., in everydirection) and UE 115-a may report a beam which the UE can receive(e.g., via receive beam 210-a or 210-b) with a signal quality above athreshold, or may report the strongest received beam. These transmitbeams 205 may be broadcast beams directed to one or more UEs 115 andmay, in some cases, each be associated with an SS block 225.

Additionally, base station 105-a may utilize one or more portions of thechannel frequency bandwidth (e.g., associated with downlinkcommunications 215), which may in some cases be referred to as a BWP fordownlink transmissions 220. A BWP may be configured, for example,according to a size of the channel frequency bandwidth, a size ofdownlink transmissions 220, capabilities of the UE 115-a or of other UEs115, etc.

SS blocks 225 and downlink transmissions 220 may be sent according tosome transmission attributes including, for example, a SCS, a beamdirection (e.g., associated with the transmission and/or reception ofthe SS block 225 or downlink transmission 220), etc. For example, SSblocks 225 may be transmitted according to a SCS of 15 kHz or 30 kHz SCSfor operating frequencies less than 6 GHz, and a SCS of 120 kHz or 240kHz for operating frequencies greater than 6 GHz. A UE 115 may identifythe transmission attributes via implicit or explicit information. Forexample, the UE 115 may be cross carrier scheduled to a carrier and mayreceive information regarding the transmission attributes of the carrierprior to receiving the SS block. Additionally or alternatively, the UE115 may monitor the carrier for SS blocks according to one or moretransmission attributes and may thus detect the transmission attributesimplicitly by detecting the SS blocks. Additionally, downlinktransmissions 220 (e.g., PDSCH, PDCCH, CSI-RS, etc. transmitted withinone or more configured BWPs) may be associated with differenttransmission attributes. For example, downlink transmissions 220 may betransmitted according to a different SCS (compared to, e.g., the SCS ofthe transmitted SS blocks 225), a different transmit beam 205, adifference receive beam 210, etc. Generally, transmission attributes forSS blocks may be referred to as SS block transmission attributes,transmission attributes included in a configuration for a BWP of acarrier may be referred to as BWP transmission attributes, andtransmission attributes associated with a channel or signal may bereferred to as channel or signal attributes. A set of transmissionattributes may also be referred to as a numerology. Techniques describedherein provide for efficient handling or management of FDMcommunications in scenarios where SS blocks 225 and other downlinktransmissions 220 are associated with mixed numerologies (e.g.,transmission parameters, characteristics, etc.).

For example, a base station 105-a may identify a configuration for a BWP(e.g., of a carrier) that includes one or more BWP transmissionattributes for transmissions within the BWP. That is, the base station105-a may configure transmission attributes for downlink transmissions220 within a BWP. For example, the base station 105-a may associate aSCS with the configured BWP, or may configure channels or signals fortransmission via the BWP with transmission attributes. Additionally oralternatively, the base station 105-a may associate a beam direction(e.g., a beam ID associated with a transmit beam 205, a receive beam210, or an active beam pair) with the configured BWP.

Further, The UE 115 may identify the one or more BWP transmissionattributes based on a BWP configuration that may be determined by theUE, for example, from a PBCH payload included as a part of thetransmitted SS block. As such, the BWP transmission attributes can beidentified based on a signal, such as the SS block transmission. Basestation 105-a may transmit a grant for the downlink transmission 220 toUE 115-a. In some examples, the grant may indicate resources thatoverlap in time with SS blocks 225 intended for the UE 115-a (e.g.,FDM). UE 115-a may identify SS block 225 resources (e.g., symbol periodson which SS block 225 is transmitted) via remaining minimum systeminformation (RMSI) or RRC configuration and may identify timing ofdownlink transmissions 220 via the received grant. If thetime-overlapping downlink transmission 220 and SS block 225 areassociated with the same transmission attributes (e.g., the same SCS),the FDM may not present any problems for reception by UEs 115. However,in cases where downlink transmission 220 and SS block 225 are associatedwith different or mixed transmission attributes, some UEs 115 may not becapable of processing FDM signals having mixed attributes. For example,a UE 115 that receives multiple signals that are FDMed with differentSCSs may need to run separate inverse discrete Fourier transform (IDFT)or inverse fast Fourier transform (IFFT) operations to demodulate thedifferent signals. Some UEs may not have sufficient processing resourcesto perform the parallel operations. Techniques to handle such FDM (e.g.,with mixed transmission attributes) may be employed, as discussed inmore detail below with reference to FIGS. 3A-3C. In yet other cases, aUE may not support such FDM (e.g. of resources of downlink transmissions220 overlapping with SS blocks 225 in time) and PDSCH grants foroverlapping resources may be rejected.

In some cases, the transmission attributes may be configured based on aUE capabilities indication. For example, the base station 105-a mayelect transmission attributes (e.g., SS block transmission attributesand/or BWP transmission attributes) for a downlink transmission 220based on a received capabilities message from UE 115-a. In some cases,the capabilities message may indicate whether the UE supports FDM,supports FDM with mixed transmission attributes, supports TDM oftransmission attributes within grants, etc. Some techniques describedherein may thus be elected or ruled out based on such capabilitiesindicated by a UE. For example, if a UE indicates it does not supportFDM reception over different beam directions, a base station may use thesame beam direction (e.g., beam ID) for both SS blocks 225 and downlinktransmissions 220 where FDM is used. As another example, if a UEindicates it cannot support FDM with mixed transmission attributes, thebase station 105 may transmit downlink transmissions 220 that are FDMedwith the SS block using SS block transmission attributes (with possibleTDM of transmission attributes within downlink transmissions 220). Incases in which TDM is used for mixed beams (e.g., using differenttransmit beams 205 and/or receive beams 210) within a downlinktransmission 220, separate demodulation reference signals (DMRSs) may beused in each of the TDMed portions (e.g., to enable channel estimationfor each portion).

In some cases, downlink transmissions 220 may not be FDMed with SSblocks 225 for a given UE 115 (e.g., in cases where the UE 115 indicatesit is not capable of supporting FDM). In such cases, the base station105-a may not transmit downlink transmissions 220 (e.g., PDSCH) duringany overlapping symbol periods for which SS blocks 225 are scheduled.Such a UE 115 may reject any grant for a downlink transmission whichindicates that the transmission will overlap with SS blocks that it isexpected to monitor. For example, the UE 115 may treat the grant asbeing falsely decoded (e.g., a false CRC-pass during PDCCH decoding).

It is to be understood that while the examples above are described interms of downlink transmissions (i.e., such that the transmit beams 205originate at the base station 105-a), analogous considerations foruplink transmissions are included in the scope of the presentdisclosure.

FIGS. 3A, 3B, and 3C illustrate examples 300-a, 300-b, and 300-c of FDMfor BWP transmissions with mixed attributes in accordance with aspectsof the present disclosure. The examples of FIGS. 3A-3C may implementaspects of wireless communications system 100 and wirelesscommunications system 200. Generally, transmission attributes for SSblocks may be referred to as SS attributes 305, and transmissionattributes included in a configuration for a BWP of a carrier (e.g., ortransmission attributes for transmissions within a BWP) may be referredto as BWP attributes 310. Techniques described herein provide threeexamples for efficient handling or management of FDM communications inscenarios where SS blocks 315 and other downlink transmissions 320 areassociated with mixed transmission attributes (e.g., transmissionparameters, characteristics, etc., which may refer to SCS, transmit beamID, received beam ID, beam pair ID, etc.). In some cases, the downlinktransmissions may be multiplexed with the SS blocks according to ascheme or pattern (e.g., FDM and/or TDM). In examples 300-a, 300-b, and300-c, frequency (e.g., kHz) may generally be represented along thevertical axis and time (e.g., seconds) may generally be representedalong the horizontal axis.

FIG. 3A illustrates an example 300-a in which a downlink transmission320-a is scheduled within a BWP 325-a (e.g., via a base station 105 or agrant from a base station 105). The downlink transmission 320-a is FDMedwith an SS block 315-a for a set of time resources 330-a. In some cases,the set of time resources 330-a may be referred to as a FDM timeduration. According to the techniques shown in example 300-a, the entiredownlink transmission 320-a may be transmitted (e.g., by a base station105) using one or more SS attributes 305. That is, both the set of timeresources 330-a (e.g., FDM portion) of downlink transmission 320-a aswell as the remaining portion (e.g., remaining resources of the downlinktransmission 320-a not overlapping in time with the SS block 315-a) maybe associated with the SS attributes 305. For example, there may be nomixed numerology associated with the FDM region (e.g., the set of timeresources 330-a), as the FDM region may be associated with only SSattributes 305. Further, a subsequent downlink transmission 320-b mayalso be scheduled in the BWP 325-a (e.g., at a time following thedownlink transmission 320-a). In some cases, the downlink transmission320-b may be a subsequent downlink transmission for the same UE thatdoes not overlap in time with SS block 315-a, and thus may use the DLBWP attributes 310. Additionally, in some cases BWP 325-a may includeadditional transmissions (not shown) for different UEs, some of whichmay be FDMed with the downlink transmission 320-a. The base station mayinsert guardband in the frequency domain between FDM transmissionshaving some mixed attributes (e.g., guardband may be inserted for FDM ofmixed SCS transmissions but not between FDM of mixed beam direction,etc.).

FIG. 3A also illustrates SS blocks (dashed) that may be present (e.g.,or sent by a serving base station) that are not intended for the UEreceiving the downlink transmission 320-a. As discussed above, such SSblocks not directed to the relevant UE do not contribute to FDMscenarios and are not considered in transmission attribute selection fordownlink transmissions 320 intended for the UE. That is, SS block 315-bmay be intended for or transmitted to some other neighboring UE.Although SS block 315-b may overlap in time with downlink transmission320-b, downlink transmission 320-b may still be associated with BWPattribute 310 (e.g., thus the technique of example 300-a, as applied todownlink transmission 320-a, may not apply to downlink transmission320-b as the UE receiving both downlink transmission 320-a and downlinktransmission 320-b may not be monitoring for SS block 315-b). In oneexample, techniques described with reference to example 300-a may beelected when a UE indicates (e.g., via a capability message) that itsupports FDM, but does not support FDM with mixed attributes (e.g.,mixed numerology).

FIG. 3B illustrates an example 300-b where a downlink transmission 320-cis scheduled within a BWP 325-b (e.g., via a base station 105 or a grantfrom a base station 105). The downlink transmission 320-c is FDMed withan SS block 315-c for a set of time resources 330-b. In some cases, theset of time resources 330-b may be referred to as a FDM time duration.According to the techniques shown in example 300-b, the portion ofdownlink transmission 320-c associated with the set of time resources330-b (e.g., FDM portion) may be associated with SS attributes 305.However, the remaining portion (e.g., remaining resources of downlinktransmission 320-c not overlapping in time with SS block 315-c) may beassociated with BWP attributes 310. Thus, there may be no mixednumerology associated with the FDM region (e.g., the set of timeresources 330-b), as the FDM region may be associated with only SSattributes 305. However, there are TDM regions of mixed numerologywithin downlink transmission 320-c. Further, a subsequent downlinktransmission 320-d may also be scheduled in the BWP 325-b (e.g., at atime following the downlink transmission 320-c). As illustrated in FIG.3B, downlink transmission 320-d may follow a combined TDM and FDM schemewith SS block 315-c.

FIG. 3B also illustrates SS blocks (dashed) that may be present (e.g.,or sent by a serving base station) that are not intended for the UEreceiving the downlink transmission 320-c. As discussed above, such SSblocks not directed to the UE of relevance do not contribute to FDMscenarios nor to transmission attribute selection for downlinktransmissions 320 intended for the UE, etc. That is, dashed SS blocksshown may be intended for or transmitted to some other neighboring UE.Although such SS blocks intended for other UEs may overlap in time withdownlink transmission 320-d, downlink transmission 320-d may still beassociated with BWP attribute 310 (e.g., thus the technique of example300-b, as applied to downlink transmission 320-c, may not apply todownlink transmission 320-d as the UE receiving both downlinktransmission 320-c and downlink transmission 320-d may not be monitoringfor SS blocks intended for other UEs). In one example, techniquesdescribed with reference to example 300-b may be elected when a UEindicates (e.g., via a capability message) that it supports TDM mixednumerology and FDM, but does not support FDM with mixed numerology.Further, in the example 300-b, although FDM mixed numerology may not besupported, TDM mixed numerology (e.g., within a single downlink packet(e.g., within downlink transmission 320-c) may be utilized. Note thatsome UEs may be limited in capability and may not be able to receive TDMmixed numerology. When the scheme in FIG. 3B is used, such a UE rejectsany grant indicating a data transmission that overlaps only partiallywith the SS blocks, but accepts grants indicating data transmissionsthat completely overlap with the SS blocks or are completelynon-overlapping with SS blocks. As described above, SS blocks in thiscontext refers only to SS blocks that the UE is expected to receive ormonitor.

FIG. 3C illustrates an example 300-c where a downlink transmission 320-eis scheduled within a BWP 325-c (e.g., via a base station 105 or a grantfrom a base station 105). The downlink transmission 320-e is FDMed withan SS block 315-d for a set of time resources 330-c. In some cases, theset of time resources 330-c may be referred to as a FDM time duration.According to the techniques shown in example 300-c, the portion ofdownlink transmission 320-e associated with the set of time resources330-c (e.g., FDM portion), as well as the remaining portion (e.g.,remaining resources of downlink transmission 320-e not overlapping withSS block 315-d) may be associated with BWP attributes 310. Thetechniques shown in example 300-c may result in mixed numerologyassociated with the FDM region (e.g., the set of time resources 330-c),as the FDM region may be associated with both SS attributes 305 and BWPattributes 310. Further, a subsequent downlink transmission 320-f mayalso be scheduled in the BWP 325-c (e.g., at a time following thedownlink transmission 320-e). As illustrated in FIG. 3C, downlinktransmission 320-f may follow a combined TDM and FDM scheme with respectto SS block 315-d.

FIG. 3C also illustrates SS blocks (dashed) that may be present (e.g.,or sent by a serving base station) that are not intended for the UEreceiving the downlink transmission 320-e or 320-f. As discussed above,such SS blocks not directed to the UE of relevance do not contribute toFDM scenarios, nor to transmission attribute selection for downlinktransmissions 320 intended for the UE. In one example, techniquesdescribed with reference to example 300-c may be elected when a UEindicates (e.g., via a capability message) that it supports FDM withmixed numerology. In some cases, the base station may also ensure asufficient guard band between FDMed mixed numerologies (e.g., guardbandmay be inserted for FDM of mixed SCS transmissions but not between FDMof mixed beam direction, etc.).

FIG. 4 shows a block diagram 400 of a wireless device 405 that supportsFDM for BWP transmissions with mixed attributes in accordance withaspects of the present disclosure. Wireless device 405 may be an exampleof aspects of a UE 115 as described herein. Wireless device 405 mayinclude receiver 410, UE communications manager 415, and transmitter420. Wireless device 405 may also include a processor. Each of thesecomponents may be in communication with one another (e.g., via one ormore buses).

Receiver 410 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to FDM for BWPtransmissions with mixed attributes, etc.). Information may be passed onto other components of the device. The receiver 410 may be an example ofaspects of the transceiver 735 described with reference to FIG. 7. Thereceiver 410 may utilize a single antenna or a set of antennas.

UE communications manager 415 may be an example of aspects of the UEcommunications manager 715 described with reference to FIG. 7. UEcommunications manager 415 and/or at least some of its varioussub-components may be implemented in hardware, software executed by aprocessor, firmware, or any combination thereof. If implemented insoftware executed by a processor, the functions of the UE communicationsmanager 415 and/or at least some of its various sub-components may beexecuted by a general-purpose processor, a digital signal processor(DSP), an application-specific integrated circuit (ASIC), anfield-programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described in thepresent disclosure. The UE communications manager 415 and/or at leastsome of its various sub-components may be physically located at variouspositions, including being distributed such that portions of functionsare implemented at different physical locations by one or more physicaldevices. In some examples, UE communications manager 415 and/or at leastsome of its various sub-components may be a separate and distinctcomponent in accordance with various aspects of the present disclosure.In other examples, UE communications manager 415 and/or at least some ofits various sub-components may be combined with one or more otherhardware components, including but not limited to an I/O component, atransceiver, a network server, another computing device, one or moreother components described in the present disclosure, or a combinationthereof in accordance with various aspects of the present disclosure.

In a first example, the UE communications manager 415 may identify aconfiguration for a BWP of a carrier. The configuration may include afirst value for a transmission attribute for transmissions within theBWP. The UE communications manager 415 may receive a grant for adownlink transmission. In some cases, the downlink transmission may bescheduled for a set of resources in the BWP that are overlapping in timewith a SS block for the carrier. The SS block may be transmitted using asecond value for the transmission attribute. The UE communicationsmanager 415 may then receive the downlink transmission, where thereceiving includes applying the second value for the transmissionattribute for at least a portion of the set of resources.

In a second example, the UE communications manager 415 may receive asynchronization signal block for a carrier, the synchronization signalblock associated with synchronization signal block transmissionattributes, identify one or more BWP transmission attributes fortransmissions within a BWP of the carrier, and receive a transmissionover the BWP of the carrier based on the synchronization signal blocktransmission attributes and the one or more BWP transmission attributes,where the transmission may be multiplexed with the synchronizationsignal block according to a pattern selected from a plurality ofpredefined multiplexing schemes including a time division multiplexingscheme and a frequency division multiplexing scheme.

Transmitter 420 may transmit signals generated by other components ofthe device. In some examples, the transmitter 420 may be collocated witha receiver 410 in a transceiver module. For example, the transmitter 420may be an example of aspects of the transceiver 735 described withreference to FIG. 7. The transmitter 420 may utilize a single antenna ora set of antennas.

FIG. 5 shows a block diagram 500 of a wireless device 505 that supportsFDM for BWP transmissions with mixed attributes in accordance withaspects of the present disclosure. Wireless device 505 may be an exampleof aspects of a wireless device 405 or a UE 115 as described withreference to FIG. 4. Wireless device 505 may include receiver 510, UEcommunications manager 515, and transmitter 520. Wireless device 505 mayalso include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

Receiver 510 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to FDM for BWPtransmissions with mixed attributes, etc.). Information may be passed onto other components of the device. The receiver 510 may be an example ofaspects of the transceiver 735 described with reference to FIG. 7. Thereceiver 510 may utilize a single antenna or a set of antennas.

UE communications manager 515 may be an example of aspects of the UEcommunications manager 715 described with reference to FIG. 7. UEcommunications manager 515 may also include BWP manager 525, grantmanager 530, and transmission attribute manager 535.

In a first example, the BWP manager 525 may identify a configuration fora BWP of a carrier, the configuration may include a first value for atransmission attribute for transmissions within the BWP. In some cases,the transmission attribute may include a SCS, a reception beamdirection, etc.

In a second example, the BWP manager 525 may receive a synchronizationsignal block for a carrier, the synchronization signal block associatedwith synchronization signal block transmission attributes and identifyone or more BWP transmission attributes for transmissions within a BWPof the carrier.

In the first example, the grant manager 530 may receive a grant for adownlink transmission, the downlink transmission scheduled for a set ofresources in the BWP that are overlapping in time with a SS block forthe carrier, the SS block being transmitted using a second value for thetransmission attribute.

In the first example, the transmission attribute manager 535 may receivethe downlink transmission, where the receiving includes applying thesecond value for the transmission attribute for at least a portion ofthe set of resources. In some cases, the receiving the downlinktransmission includes applying the second value for the transmissionattribute for all of the set of resources. In some cases, the receivingthe downlink transmission includes applying the first value for thetransmission attribute for a first portion of the set of resources notoverlapping in time with the SS block and the second value for thetransmission attribute for a second portion of the set of resourcesoverlapping in time with the SS block.

In the second example, the transmission attribute manager 535 mayreceive a transmission over the BWP of the carrier based on thesynchronization signal block transmission attributes and the one or moreBWP transmission attributes, where the transmission may be multiplexedwith the synchronization signal block according to a pattern selectedfrom a plurality of predefined multiplexing schemes including a timedivision multiplexing scheme and a frequency division multiplexingscheme.

Transmitter 520 may transmit signals generated by other components ofthe device. In some examples, the transmitter 520 may be collocated witha receiver 510 in a transceiver module. For example, the transmitter 520may be an example of aspects of the transceiver 735 described withreference to FIG. 7. The transmitter 520 may utilize a single antenna ora set of antennas.

FIG. 6 shows a block diagram 600 of a UE communications manager 615 thatsupports FDM for BWP transmissions with mixed attributes in accordancewith aspects of the present disclosure. The UE communications manager615 may be an example of aspects of a UE communications manager 415, aUE communications manager 515, or a UE communications manager 715described with reference to FIGS. 4, 5, and 7. The UE communicationsmanager 615 may include BWP manager 620, grant manager 625, andtransmission attribute manager 630. Each of these modules maycommunicate, directly or indirectly, with one another (e.g., via one ormore buses).

The BWP manager 620 may identify a configuration for a BWP of a carrier,the configuration including a first value for a transmission attributefor transmissions within the BWP. In some cases, the transmissionattribute includes a SCS. In some cases, the transmission attributeincludes a transmission beam direction or a reception beam direction.

Additionally or alternatively, the BWP manager 620 may receive asynchronization signal block for a carrier, the synchronization signalblock associated with synchronization signal block transmissionattributes. In some cases, the BWP manager 620 may identify one or moreBWP transmission attributes for transmissions within a BWP of thecarrier. In some cases, the synchronization signal block transmissionattributes include a first SCS and the one or more BWP transmissionattributes include a second SCS. In some cases, the first SCS and thesecond SCS are different. In some cases, the one or more BWPtransmission attributes include a transmission beam direction or areception beam direction.

Grant manager 625 may receive a grant for a downlink transmission, thedownlink transmission scheduled for a set of resources in the BWP thatare overlapping in time with a SS block for the carrier. The SS blockmay be transmitted using a second value for the transmission attribute.

The transmission attribute manager 630 may receive the downlinktransmission, where the receiving includes applying the second value forthe transmission attribute for at least a portion of the set ofresources. In some cases, the receiving the downlink transmissionincludes applying the second value for the transmission attribute forall of the set of resources. In some cases, the receiving the downlinktransmission includes applying the first value for the transmissionattribute for a first portion of the set of resources not overlapping intime with the SS block and applying the second value for thetransmission attribute for a second portion of the set of resourcesoverlapping in time with the SS block.

Additionally or alternatively, the transmission attribute manager 630may receive a transmission over the BWP of the carrier based on thesynchronization signal block transmission attributes and the one or moreBWP transmission attributes, where the transmission may be multiplexedwith the synchronization signal block according to a pattern selectedfrom a plurality of predefined multiplexing schemes including a timedivision multiplexing scheme and a frequency division multiplexingscheme. In some cases, the transmission includes a downlink controlchannel transmission. In some cases, the transmission includes adownlink shared channel transmission.

FIG. 7 shows a diagram of a system 700 including a device 705 thatsupports FDM for BWP transmissions with mixed attributes in accordancewith aspects of the present disclosure. Device 705 may be an example ofor include the components of wireless device 405, wireless device 505,or a UE 115 as described above, e.g., with reference to FIGS. 4 and 5.Device 705 may include components for bi-directional voice and datacommunications including components for transmitting and receivingcommunications, including UE communications manager 715, processor 720,memory 725, software 730, transceiver 735, antenna 740, and I/Ocontroller 745. These components may be in electronic communication viaone or more buses (e.g., bus 710). Device 705 may communicate wirelesslywith one or more base stations 105.

Processor 720 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a central processing unit (CPU), amicrocontroller, an ASIC, an FPGA, a programmable logic device, adiscrete gate or transistor logic component, a discrete hardwarecomponent, or any combination thereof). In some cases, processor 720 maybe configured to operate a memory array using a memory controller. Inother cases, a memory controller may be integrated into processor 720.Processor 720 may be configured to execute computer-readableinstructions stored in a memory to perform various functions (e.g.,functions or tasks supporting FDM for BWP transmissions with mixedattributes).

Memory 725 may include random access memory (RAM) and read only memory(ROM). The memory 725 may store computer-readable, computer-executablesoftware 730 including instructions that, when executed, cause theprocessor to perform various functions described herein. In some cases,the memory 725 may contain, among other things, a basic input/outputsystem (BIOS) which may control basic hardware or software operationsuch as the interaction with peripheral components or devices.

Software 730 may include code to implement aspects of the presentdisclosure, including code to support FDM for BWP transmissions withmixed attributes. Software 730 may be stored in a non-transitorycomputer-readable medium such as system memory or other memory. In somecases, the software 730 may not be directly executable by the processorbut may cause a computer (e.g., when compiled and executed) to performfunctions described herein.

Transceiver 735 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 735 may represent a wireless transceiver and may communicatebi-directionally with another wireless transceiver. The transceiver 735may also include a modem to modulate the packets and provide themodulated packets to the antennas for transmission, and to demodulatepackets received from the antennas.

In some cases, the wireless device may include a single antenna 740.However, in some cases the device may have more than one antenna 740,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

I/O controller 745 may manage input and output signals for device 705.I/O controller 745 may also manage peripherals not integrated intodevice 705. In some cases, I/O controller 745 may represent a physicalconnection or port to an external peripheral. In some cases, I/Ocontroller 745 may utilize an operating system such as iOS®, ANDROID®,MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operatingsystem. In other cases, I/O controller 745 may represent or interactwith a modem, a keyboard, a mouse, a touchscreen, or a similar device.In some cases, I/O controller 745 may be implemented as part of aprocessor. In some cases, a user may interact with device 705 via I/Ocontroller 745 or via hardware components controlled by I/O controller745.

FIG. 8 shows a block diagram 800 of a wireless device 805 that supportsFDM for BWP transmissions with mixed attributes in accordance withaspects of the present disclosure. Wireless device 805 may be an exampleof aspects of a base station 105 as described herein. Wireless device805 may include receiver 810, base station communications manager 815,and transmitter 820. Wireless device 805 may also include a processor.Each of these components may be in communication with one another (e.g.,via one or more buses).

Receiver 810 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to FDM for BWPtransmissions with mixed attributes, etc.). Information may be passed onto other components of the device. The receiver 810 may be an example ofaspects of the transceiver 1135 described with reference to FIG. 11. Thereceiver 810 may utilize a single antenna or a set of antennas.

Base station communications manager 815 may be an example of aspects ofthe base station communications manager 1115 described with reference toFIG. 11. Base station communications manager 815 and/or at least some ofits various sub-components may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions of thebase station communications manager 815 and/or at least some of itsvarious sub-components may be executed by a general-purpose processor, aDSP, an ASIC, an FPGA or other programmable logic device, discrete gateor transistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described in the presentdisclosure. The base station communications manager 815 and/or at leastsome of its various sub-components may be physically located at variouspositions, including being distributed such that portions of functionsare implemented at different physical locations by one or more physicaldevices. In some examples, base station communications manager 815and/or at least some of its various sub-components may be a separate anddistinct component in accordance with various aspects of the presentdisclosure. In other examples, base station communications manager 815and/or at least some of its various sub-components may be combined withone or more other hardware components, including but not limited to anI/O component, a transceiver, a network server, another computingdevice, one or more other components described in the presentdisclosure, or a combination thereof in accordance with various aspectsof the present disclosure.

The base station communications manager 815 may identify a configurationfor a BWP of a carrier, the configuration may include a first value fora transmission attribute for transmissions within the BWP. The basestation communications manager 815 may transmit a grant for a firstdownlink transmission in the BWP to a first UE. In some cases, the firstdownlink transmission may be scheduled for a first set of resources thatare overlapping in time with a SS block for the carrier (e.g., the SSblock may be transmitted using a second value for the transmissionattribute). Base station communications manager 815 may then transmitthe first downlink transmission, where the transmitting includesapplying the second value for the transmission attribute for at least aportion of the first set of resources.

The base station communications manager 815 may also identify aconfiguration for a BWP of a carrier, the configuration including afirst value for a transmission attribute for transmissions within theBWP. The base station communications manager 815 may transmit a grantfor a first downlink transmission in the BWP to a first UE, the firstdownlink transmission scheduled for a first set of resources that areoverlapping in time with a SS block for the carrier (e.g., the SS blockbeing transmitted using a second value for the transmission attribute).The base station communications manager 815 may then transmit the firstdownlink transmission, where the transmitting includes applying thefirst value for the transmission attribute for the first set ofresources and inserting a guard band in the frequency domain between thefirst downlink transmission and the SS block.

Additionally or alternatively, the base station communications manager815 may transmit, to a UE, a synchronization signal block for a carrier,the synchronization signal block associated with synchronization signalblock transmission attributes and configure one or more BWP transmissionattributes for transmissions within a BWP of the carrier. The basestation communications manager 815 may transmit, to the UE, atransmission over the BWP of the carrier based on the synchronizationsignal block transmission attributes and the one or more BWPtransmission attributes, where the transmission may be multiplexed withthe synchronization signal block according to a pattern selected from aplurality of predefined multiplexing schemes including a time divisionmultiplexing scheme and a frequency division multiplexing scheme.

Further additionally or alternatively, the base station communicationsmanager 815 may also transmit, to a UE, a synchronization signal blockfor a carrier, the synchronization signal block associated withsynchronization signal block transmission attributes and configure oneor more BWP transmission attributes for transmissions within a BWP ofthe carrier. The base station communications manager 815 may transmit,to the UE, a downlink transmission over the BWP of the carrier based onthe synchronization signal block transmission attributes and the one ormore BWP transmission attributes, where the downlink transmission ismultiplexed with the synchronization signal block according to a patternselected from a plurality of predefined multiplexing schemes including atime division multiplexing scheme and a frequency division multiplexingscheme, the pattern including an inserted guard band in the frequencydomain between the downlink transmission and the synchronization signalblock.

Transmitter 820 may transmit signals generated by other components ofthe device. In some examples, the transmitter 820 may be collocated witha receiver 810 in a transceiver module. For example, the transmitter 820may be an example of aspects of the transceiver 1135 described withreference to FIG. 11. The transmitter 820 may utilize a single antennaor a set of antennas.

FIG. 9 shows a block diagram 900 of a wireless device 905 that supportsFDM for BWP transmissions with mixed attributes in accordance withaspects of the present disclosure. Wireless device 905 may be an exampleof aspects of a wireless device 805 or a base station 105 as describedwith reference to FIG. 8. Wireless device 905 may include receiver 910,base station communications manager 915, and transmitter 920. Wirelessdevice 905 may also include a processor. Each of these components may bein communication with one another (e.g., via one or more buses).

Receiver 910 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to FDM for BWPtransmissions with mixed attributes, etc.). Information may be passed onto other components of the device. The receiver 910 may be an example ofaspects of the transceiver 1135 described with reference to FIG. 11. Thereceiver 910 may utilize a single antenna or a set of antennas.

Base station communications manager 915 may be an example of aspects ofthe base station communications manager 1115 described with reference toFIG. 11. Base station communications manager 915 may also include BWPmanager 925, grant manager 930, downlink transmission manager 935, andtransmission attribute manager 940.

In a first example, the BWP manager 925 may identify a configuration fora BWP of a carrier, the configuration including a first value for atransmission attribute for transmissions within the BWP.

In a second example, the BWP manager 925 may transmit, to a UE, asynchronization signal block for a carrier, the synchronization signalblock associated with synchronization signal block transmissionattributes and configure one or more BWP transmission attributes fortransmissions within a BWP of the carrier.

In a third example, the BWP manager 925 may similarly transmit, to a UE,a synchronization signal block for a carrier, the synchronization signalblock associated with synchronization signal block transmissionattributes and configure one or more BWP transmission attributes fortransmissions within a BWP of the carrier.

In the first example, the grant manager 930 may transmit a grant for afirst downlink transmission in the BWP to a first UE, the first downlinktransmission scheduled for a first set of resources that are overlappingin time with a SS block for the carrier, the SS block being transmittedusing a second value for the transmission attribute.

In the first example, the downlink transmission manager 935 may transmitthe first downlink transmission, where the transmitting includesapplying the second value for the transmission attribute for at least aportion of the first set of resources.

In the second example, the downlink transmission manager 935 maytransmit, to the UE, a transmission over the BWP of the carrier based onthe synchronization signal block transmission attributes and the one ormore BWP transmission attributes, where the transmission may bemultiplexed with the synchronization signal block according to a patternselected from a plurality of predefined multiplexing schemes including atime division multiplexing scheme and a frequency division multiplexingscheme.

In the third example, the downlink transmission manager 935 maytransmit, to the UE, a downlink transmission over the BWP of the carrierbased on the synchronization signal block transmission attributes andthe one or more BWP transmission attributes, where the downlinktransmission is multiplexed with the synchronization signal blockaccording to a pattern selected from a plurality of predefinedmultiplexing schemes including a time division multiplexing scheme and afrequency division multiplexing scheme, the pattern including aninserted guard band in the frequency domain between the downlinktransmission and the synchronization signal block.

In the first example, the transmission attribute manager 940 maytransmit a second downlink transmission to a second UE, the seconddownlink transmission overlapping in time with the first downlinktransmission and not overlapping in time with the SS block, where thetransmitting the second downlink transmission includes inserting a guardband in the frequency domain between the first downlink transmission andthe second downlink transmission and transmit the first downlinktransmission. In some cases, the transmitting includes applying thefirst value for the transmission attribute for the first set ofresources and inserting a guard band in the frequency domain between thefirst downlink transmission and the SS block. In some cases, thetransmitting the first downlink transmission includes: applying thesecond value for the transmission attribute for all of the first set ofresources. In some cases, the transmitting the first downlinktransmission includes: applying the first value for the transmissionattribute for a first portion of the first set of resources notoverlapping in time with the SS block and the second value for thetransmission attribute for a second portion of the first set ofresources overlapping in time with the SS block. In some cases, thetransmission attribute includes a SCS. In some cases, the transmissionattribute includes a transmission beam direction or a reception beamdirection. In some cases, the transmitting the first downlinktransmission applying the first value for the transmission attribute forthe first set of resources is based on a received capability messagefrom the first UE indicating support for frequency division multiplexingof the first and second values for the transmission attribute. In somecases, the transmission attribute includes a SCS. In some cases, thetransmission attribute includes a transmission beam direction or areception beam direction.

Transmitter 920 may transmit signals generated by other components ofthe device. In some examples, the transmitter 920 may be collocated witha receiver 910 in a transceiver module. For example, the transmitter 920may be an example of aspects of the transceiver 1135 described withreference to FIG. 11. The transmitter 920 may utilize a single antennaor a set of antennas.

FIG. 10 shows a block diagram 1000 of a base station communicationsmanager 1015 that supports FDM for BWP transmissions with mixedattributes in accordance with aspects of the present disclosure. Thebase station communications manager 1015 may be an example of aspects ofa base station communications manager 1115 described with reference toFIGS. 8, 9, and 11. The base station communications manager 1015 mayinclude BWP manager 1020, grant manager 1025, downlink transmissionmanager 1030, and transmission attribute manager 1035. Each of thesemodules may communicate, directly or indirectly, with one another (e.g.,via one or more buses).

In some cases, the BWP manager 1020 may identify a configuration for aBWP of a carrier, the configuration including a first value for atransmission attribute for transmissions within the BWP.

Additionally or alternatively, the BWP manager 1020 may transmit, to aUE, a synchronization signal block for a carrier, the synchronizationsignal block associated with synchronization signal block transmissionattributes. In some examples, the BWP manager 1020 may configure one ormore BWP transmission attributes for transmissions within a BWP of thecarrier. In some cases, the synchronization signal block transmissionattributes include a first SCS and the one or more BWP transmissionattributes include a second SCS. In some cases, the first SCS and thesecond SCS are different. In some cases, the one or more BWPtransmission attributes include a transmission beam direction or areception beam direction.

Grant manager 1025 may transmit a grant for a first downlinktransmission in the BWP to a first UE, the first downlink transmissionscheduled for a first set of resources that are overlapping in time witha SS block for the carrier, the SS block being transmitted using asecond value for the transmission attribute.

Downlink transmission manager 1030 may transmit the first downlinktransmission, where the transmitting includes applying the second valuefor the transmission attribute for at least a portion of the first setof resources.

Additionally or alternatively, the downlink transmission manager 1030may transmit, to the UE, a downlink transmission over the BWP of thecarrier based on the synchronization signal block transmissionattributes and the one or more BWP transmission attributes, where thedownlink transmission is multiplexed with the synchronization signalblock according to a pattern selected from a plurality of predefinedmultiplexing schemes including a time division multiplexing scheme and afrequency division multiplexing scheme, the pattern including aninserted guard band in the frequency domain between the downlinktransmission and the synchronization signal block.

The transmission attribute manager 1035 may transmit a first downlinktransmission, where the transmitting includes applying the first valuefor the transmission attribute for the first set of resources andinserting a guard band in the frequency domain between the firstdownlink transmission and the SS block. In some cases, the transmittingthe first downlink transmission includes applying the second value forthe transmission attribute for all of the first set of resources. Insome cases, the transmitting the first downlink transmission includesapplying the first value for the transmission attribute for a firstportion of the first set of resources not overlapping in time with theSS block and the second value for the transmission attribute for asecond portion of the first set of resources overlapping in time withthe SS block. In some cases, the transmission attribute includes a SCS.In some cases, the transmission attribute includes a transmission beamdirection or a reception beam direction. In some cases, the transmittingthe first downlink transmission applying the first value for thetransmission attribute for the first set of resources is based on areceived capability message from the first UE indicating support for FDMof the first and second values for the transmission attribute. In someexamples, transmission attribute manager 1035 may transmit a seconddownlink transmission to a second UE, the second downlink transmissionoverlapping in time with the first downlink transmission and notoverlapping in time with the SS block. The transmitting the seconddownlink transmission may include inserting a guard band in thefrequency domain between the first downlink transmission and the seconddownlink transmission.

Additionally or alternatively, the transmission attribute manager 1035may transmit a second transmission to a second UE, the secondtransmission overlapping in time with the transmission and notoverlapping in time with the synchronization signal block, where thetransmitting the second transmission may include inserting a guard bandin the frequency domain between the transmission and the secondtransmission.

FIG. 11 shows a diagram of a system 1100 including a device 1105 thatsupports FDM for BWP transmissions with mixed attributes in accordancewith aspects of the present disclosure. Device 1105 may be an example ofor include the components of base station 105 as described above, e.g.,with reference to FIG. 1. Device 1105 may include components forbi-directional voice and data communications including components fortransmitting and receiving communications, including base stationcommunications manager 1115, processor 1120, memory 1125, software 1130,transceiver 1135, antenna 1140, network communications manager 1145, andinter-station communications manager 1150. These components may be inelectronic communication via one or more buses (e.g., bus 1110). Device1105 may communicate wirelessly with one or more UEs 115.

Processor 1120 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, processor 1120 may be configured to operate a memoryarray using a memory controller. In other cases, a memory controller maybe integrated into processor 1120. Processor 1120 may be configured toexecute computer-readable instructions stored in a memory to performvarious functions (e.g., functions or tasks supporting FDM for BWPtransmissions with mixed attributes).

Memory 1125 may include RAM and ROM. The memory 1125 may storecomputer-readable, computer-executable software 1130 includinginstructions that, when executed, cause the processor to perform variousfunctions described herein. In some cases, the memory 1125 may contain,among other things, a BIOS which may control basic hardware or softwareoperation such as the interaction with peripheral components or devices.

Software 1130 may include code to implement aspects of the presentdisclosure, including code to support FDM for BWP transmissions withmixed attributes. Software 1130 may be stored in a non-transitorycomputer-readable medium such as system memory or other memory. In somecases, the software 1130 may not be directly executable by the processorbut may cause a computer (e.g., when compiled and executed) to performfunctions described herein.

Transceiver 1135 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 1135 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1135 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1140.However, in some cases the device may have more than one antenna 1140,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

Network communications manager 1145 may manage communications with thecore network (e.g., via one or more wired backhaul links). For example,the network communications manager 1145 may manage the transfer of datacommunications for client devices, such as one or more UEs 115.

Inter-station communications manager 1150 may manage communications withother base station 105, and may include a controller or scheduler forcontrolling communications with UEs 115 in cooperation with other basestations 105. For example, the inter-station communications manager 1150may coordinate scheduling for transmissions to UEs 115 for variousinterference mitigation techniques such as beamforming or jointtransmission. In some examples, inter-station communications manager1150 may provide an X2 or XN interface within an LTE/LTE-A or NRwireless communication network technology to provide communicationbetween base stations 105.

FIG. 12 shows a flowchart illustrating a method 1200 for FDM for BWPtransmissions with mixed attributes in accordance with aspects of thepresent disclosure. The operations of method 1200 may be implemented bya UE 115 or its components as described herein. For example, theoperations of method 1200 may be performed by a UE communicationsmanager as described with reference to FIGS. 4 through 7. In someexamples, a UE 115 may execute a set of codes to control the functionalelements of the device to perform the functions described below.Additionally or alternatively, the UE 115 may perform aspects of thefunctions described below using special-purpose hardware.

At 1205, the UE may identify a configuration for a BWP of a carrier, theconfiguration including a first value for a transmission attribute fortransmissions within the BWP. In some cases, the transmission attributemay include a SCS, a transmission beam direction, and/or a receptionbeam direction. The operations of 1205 may be performed according to themethods described herein. In certain examples, aspects of the operationsof 1205 may be performed by a BWP manager as described with reference toFIGS. 4 through 7.

At 1210, the UE may receive a grant for a downlink transmission, thedownlink transmission scheduled for a set of resources in the BWP thatare overlapping in time with a SS block for the carrier, the SS blockbeing transmitted using a second value for the transmission attribute.The operations of 1210 may be performed according to the methodsdescribed herein. In certain examples, aspects of the operations of 1210may be performed by a grant manager as described with reference to FIGS.4 through 7.

At 1215, the UE may receive the downlink transmission, where thereceiving includes applying the second value for the transmissionattribute for at least a portion of the set of resources. In some cases,at 1215, the UE may apply the second value for the transmissionattribute for all of the set of resources. In other cases, at 1215, theUE may apply the first value for the transmission attribute for a firstportion of the set of resources not overlapping in time with thesynchronization signal block and the second value for the transmissionattribute for a second portion of the set of resources overlapping intime with the synchronization signal block. The operations of 1215 maybe performed according to the methods described herein. In certainexamples, aspects of the operations of 1215 may be performed by atransmission attribute manager as described with reference to FIGS. 4through 7.

FIG. 13 shows a flowchart illustrating a method 1300 for FDM for BWPtransmissions with mixed attributes in accordance with aspects of thepresent disclosure. The operations of method 1300 may be implemented bya base station 105 or its components as described herein. For example,the operations of method 1300 may be performed by a base stationcommunications manager as described with reference to FIGS. 8 through11. In some examples, a base station 105 may execute a set of codes tocontrol the functional elements of the device to perform the functionsdescribed below. Additionally or alternatively, the base station 105 mayperform aspects of the functions described below using special-purposehardware.

At 1305, the base station may identify a configuration for a BWP of acarrier, the configuration including a first value for a transmissionattribute for transmissions within the BWP. In some cases, thetransmission attribute may include a SCS, a transmission beam direction,and/or a reception beam direction. The operations of 1305 may beperformed according to the methods described herein. In certainexamples, aspects of the operations of 1305 may be performed by a BWPmanager as described with reference to FIGS. 8 through 11.

At 1310, the base station may transmit a grant for a first downlinktransmission in the BWP to a first UE, the first downlink transmissionscheduled for a first set of resources that are overlapping in time witha SS block for the carrier, the SS block being transmitted using asecond value for the transmission attribute. The operations of 1310 maybe performed according to the methods described herein. In certainexamples, aspects of the operations of 1310 may be performed by a grantmanager as described with reference to FIGS. 8 through 11.

At 1315, the base station may transmit the first downlink transmission,where the transmitting includes applying the second value for thetransmission attribute for at least a portion of the first set ofresources. In some examples, at 1315, the base station may apply thesecond value for the transmission attribute for all of the first set ofresources. In some examples, at 1315, the base station may apply thefirst value for the transmission attribute for a first portion of thefirst set of resources not overlapping in time with the synchronizationsignal block and the second value for the transmission attribute for asecond portion of the first set of resources overlapping in time withthe synchronization signal block. The operations of 1315 may beperformed according to the methods described herein. In certainexamples, aspects of the operations of 1315 may be performed by adownlink transmission manager as described with reference to FIGS. 8through 11.

FIG. 14 shows a flowchart illustrating a method 1400 for FDM for BWPtransmissions with mixed attributes in accordance with aspects of thepresent disclosure. The operations of method 1400 may be implemented bya base station 105 or its components as described herein. For example,the operations of method 1400 may be performed by a base stationcommunications manager as described with reference to FIGS. 8 through11. In some examples, a base station 105 may execute a set of codes tocontrol the functional elements of the device to perform the functionsdescribed below. Additionally or alternatively, the base station 105 mayperform aspects of the functions described below using special-purposehardware.

At 1405, the base station may identify a configuration for a BWP of acarrier, the configuration including a first value for a transmissionattribute for transmissions within the BWP. The operations of 1405 maybe performed according to the methods described herein. In certainexamples, aspects of the operations of 1405 may be performed by a BWPmanager as described with reference to FIGS. 8 through 11.

At 1410, the base station may transmit a grant for a first downlinktransmission in the BWP to a first UE, the first downlink transmissionscheduled for a first set of resources that are overlapping in time witha SS block for the carrier, the SS block being transmitted using asecond value for the transmission attribute. The operations of 1410 maybe performed according to the methods described herein. In certainexamples, aspects of the operations of 1410 may be performed by a grantmanager as described with reference to FIGS. 8 through 11.

At 1415, the base station may transmit the first downlink transmission,where the transmitting includes applying the second value for thetransmission attribute for at least a portion of the first set ofresources. The operations of 1415 may be performed according to themethods described herein. In certain examples, aspects of the operationsof 1415 may be performed by a downlink transmission manager as describedwith reference to FIGS. 8 through 11.

At 1420, the base station may transmit a second downlink transmission toa second UE, the second downlink transmission overlapping in time withthe first downlink transmission and not overlapping in time with the SSblock, where the transmitting the second downlink transmission includesinserting a guard band in the frequency domain between the firstdownlink transmission and the second downlink transmission. Theoperations of 1420 may be performed according to the methods describedherein. In certain examples, aspects of the operations of 1420 may beperformed by a transmission attribute manager as described withreference to FIGS. 8 through 11.

In some cases, the transmitting the first downlink transmission includesapplying the second value for the transmission attribute for all of thefirst set of resources.

FIG. 15 shows a flowchart illustrating a method 1500 for FDM for BWPtransmissions with mixed attributes in accordance with aspects of thepresent disclosure. The operations of method 1500 may be implemented bya base station 105 or its components as described herein. For example,the operations of method 1500 may be performed by a base stationcommunications manager as described with reference to FIGS. 8 through11. In some examples, a base station 105 may execute a set of codes tocontrol the functional elements of the device to perform the functionsdescribed below. Additionally or alternatively, the base station 105 mayperform aspects of the functions described below using special-purposehardware.

At 1505, the base station may identify a configuration for a BWP of acarrier, the configuration including a first value for a transmissionattribute for transmissions within the BWP. The operations of 1505 maybe performed according to the methods described herein. In certainexamples, aspects of the operations of 1505 may be performed by a BWPmanager as described with reference to FIGS. 8 through 11.

At 1510, the base station may transmit a grant for a first downlinktransmission in the BWP to a first UE, the first downlink transmissionscheduled for a first set of resources that are overlapping in time witha SS block for the carrier, the SS block being transmitted using asecond value for the transmission attribute. The operations of 1510 maybe performed according to the methods described herein. In certainexamples, aspects of the operations of 1510 may be performed by a grantmanager as described with reference to FIGS. 8 through 11.

At 1515, the base station may transmit the first downlink transmission,where the transmitting includes applying the first value for thetransmission attribute for the first set of resources and inserting aguard band in the frequency domain between the first downlinktransmission and the SS block. In some examples, at 1515, the basestation may transmit the first downlink transmission applying the firstvalue for the transmission attribute for the first set of resourcesbased on a received capability message from the first UE indicatingsupport for FDM of the first and second values for the transmissionattribute. The operations of 1515 may be performed according to themethods described herein. In certain examples, aspects of the operationsof 1515 may be performed by a transmission attribute manager asdescribed with reference to FIGS. 8 through 11.

FIG. 16 shows a flowchart illustrating a method 1600 for FDM for BWPtransmissions with mixed attributes in accordance with aspects of thepresent disclosure. The operations of method 1600 may be implemented bya UE 115 or its components as described herein. For example, theoperations of method 1600 may be performed by a UE communicationsmanager as described with reference to FIGS. 4 through 7. In someexamples, a UE 115 may execute a set of codes to control the functionalelements of the device to perform the functions described below.Additionally or alternatively, the UE 115 may perform aspects of thefunctions described below using special-purpose hardware.

At 1605, the UE may receive a synchronization signal block for acarrier, the synchronization signal block associated withsynchronization signal block transmission attributes. In one example,synchronization signal block transmission attributes associated with thesynchronization signal block transmission are detected implicitly, asthe UE searches for the synchronization signal block. The operations of1605 may be performed according to the methods described herein. Incertain examples, aspects of the operations of 1605 may be performed bya BWP manager as described with reference to FIGS. 4 through 7.

At 1610, the UE may identify one or more BWP transmission attributes fortransmissions within a BWP of the carrier. The UE may identify the oneor more BWP transmission attributes based on a BWP configuration thatmay be determined by the UE, for example, from a PBCH payload includedas a part of the transmitted synchronization signal block. As such, theBWP transmission attributes can be identified based on a signal, such asthe synchronization signal block transmission. The operations of 1610may be performed according to the methods described herein. In certainexamples, aspects of the operations of 1610 may be performed by a BWPmanager as described with reference to FIGS. 4 through 7.

At 1615, the UE may receive a transmission over the BWP of the carrierbased on the synchronization signal block transmission attributes andthe one or more BWP transmission attributes, where the transmission maybe multiplexed with the synchronization signal block according to apattern selected from a plurality of predefined multiplexing schemesincluding a time division multiplexing scheme and a frequency divisionmultiplexing scheme. The operations of 1615 may be performed accordingto the methods described herein. In certain examples, aspects of theoperations of 1615 may be performed by a transmission attribute manageras described with reference to FIGS. 4 through 7.

FIG. 17 shows a flowchart illustrating a method 1700 for FDM for BWPtransmissions with mixed attributes in accordance with aspects of thepresent disclosure. The operations of method 1700 may be implemented bya base station 105 or its components as described herein. For example,the operations of method 1700 may be performed by a base stationcommunications manager as described with reference to FIGS. 8 through11. In some examples, a base station 105 may execute a set of codes tocontrol the functional elements of the device to perform the functionsdescribed below. Additionally or alternatively, the base station 105 mayperform aspects of the functions described below using special-purposehardware.

At 1705, the base station may transmit, to a UE, a synchronizationsignal block for a carrier, the synchronization signal block associatedwith synchronization signal block transmission attributes. Theoperations of 1705 may be performed according to the methods describedherein. In certain examples, aspects of the operations of 1705 may beperformed by a BWP manager as described with reference to FIGS. 8through 11.

At 1710, the base station may configure one or more BWP transmissionattributes for transmissions within a BWP of the carrier. The operationsof 1710 may be performed according to the methods described herein. Incertain examples, aspects of the operations of 1705 may be performed bya BWP manager as described with reference to FIGS. 8 through 11.

At 1715, the base station may transmit, to the UE, a transmission overthe BWP of the carrier based on the synchronization signal blocktransmission attributes and the one or more BWP transmission attributes,where the transmission may be multiplexed with the synchronizationsignal block according to a pattern selected from a plurality ofpredefined multiplexing schemes including a time division multiplexingscheme and a frequency division multiplexing scheme. The operations of1715 may be performed according to the methods described herein. Incertain examples, aspects of the operations of 1715 may be performed bya downlink transmission manager as described with reference to FIGS. 8through 11.

FIG. 18 shows a flowchart illustrating a method 1800 for FDM for BWPtransmissions with mixed attributes in accordance with aspects of thepresent disclosure. The operations of method 1800 may be implemented bya base station 105 or its components as described herein. For example,the operations of method 1800 may be performed by a base stationcommunications manager as described with reference to FIGS. 8 through11. In some examples, a base station 105 may execute a set of codes tocontrol the functional elements of the device to perform the functionsdescribed below. Additionally or alternatively, the base station 105 mayperform aspects of the functions described below using special-purposehardware.

At 1805, the base station may transmit, to a UE, a synchronizationsignal block for a carrier, the synchronization signal block associatedwith synchronization signal block transmission attributes. Theoperations of 1805 may be performed according to the methods describedherein. In certain examples, aspects of the operations of 1805 may beperformed by a BWP manager as described with reference to FIGS. 8through 11.

At 1810, the base station may configure one or more BWP transmissionattributes for transmissions within a BWP of the carrier. The operationsof 1810 may be performed according to the methods described herein. Incertain examples, aspects of the operations of 1805 may be performed bya BWP manager as described with reference to FIGS. 8 through 11.

At 1815, the base station may transmit, to the UE, a downlinktransmission over the BWP of the carrier based on the synchronizationsignal block transmission attributes and the one or more BWPtransmission attributes, where the downlink transmission is multiplexedwith the synchronization signal block according to a pattern selectedfrom a plurality of predefined multiplexing schemes including a timedivision multiplexing scheme and a frequency division multiplexingscheme, the pattern including an inserted guard band in the frequencydomain between the downlink transmission and the synchronization signalblock. The operations of 1815 may be performed according to the methodsdescribed herein. In certain examples, aspects of the operations of 1815may be performed by a downlink transmission manager as described withreference to FIGS. 8 through 11.

It should be noted that the methods described above describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Further, aspects from two or more of the methods may be combined.

Techniques described herein may be used for various wirelesscommunications systems such as code division multiple access (CDMA),time division multiple access (TDMA), frequency division multiple access(FDMA), orthogonal frequency division multiple access (OFDMA), singlecarrier frequency division multiple access (SC-FDMA), and other systems.A CDMA system may implement a radio technology such as CDMA2000,Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000,IS-95, and IS-856 standards. IS-2000 Releases may be commonly referredto as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to asCDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. A TDMA system mayimplement a radio technology such as Global System for MobileCommunications (GSM).

An OFDMA system may implement a radio technology such as Ultra MobileBroadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical andElectronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal MobileTelecommunications System (UMTS). LTE and LTE-A are releases of UMTSthat use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, NR, and GSM aredescribed in documents from the organization named “3rd GenerationPartnership Project” (3GPP). CDMA2000 and UMB are described in documentsfrom an organization named “3rd Generation Partnership Project 2”(3GPP2). The techniques described herein may be used for the systems andradio technologies mentioned above as well as other systems and radiotechnologies. While aspects of an LTE or an NR system may be describedfor purposes of example, and LTE or NR terminology may be used in muchof the description, the techniques described herein are applicablebeyond LTE or NR applications.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEs115 with service subscriptions with the network provider. A small cellmay be associated with a lower-powered base station 105, as comparedwith a macro cell, and a small cell may operate in the same or different(e.g., licensed, unlicensed, etc.) frequency bands as macro cells. Smallcells may include pico cells, femto cells, and micro cells according tovarious examples. A pico cell, for example, may cover a small geographicarea and may allow unrestricted access by UEs 115 with servicesubscriptions with the network provider. A femto cell may also cover asmall geographic area (e.g., a home) and may provide restricted accessby UEs 115 having an association with the femto cell (e.g., UEs 115 in aclosed subscriber group (CSG), UEs 115 for users in the home, and thelike). An eNB for a macro cell may be referred to as a macro eNB. An eNBfor a small cell may be referred to as a small cell eNB, a pico eNB, afemto eNB, or a home eNB. An eNB may support one or multiple (e.g., two,three, four, and the like) cells, and may also support communicationsusing one or multiple component carriers.

The wireless communications system 100 or systems described herein maysupport synchronous or asynchronous operation. For synchronousoperation, the base stations 105 may have similar frame timing, andtransmissions from different base stations 105 may be approximatelyaligned in time. For asynchronous operation, the base stations 105 mayhave different frame timing, and transmissions from different basestations 105 may not be aligned in time. The techniques described hereinmay be used for either synchronous or asynchronous operations.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the above description may berepresented by voltages, currents, electromagnetic waves, magneticfields or particles, optical fields or particles, or any combinationthereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, a FPGA or other programmablelogic device (PLD), discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but in the alternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices (e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described above can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations.

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media maycomprise RAM, ROM, electrically erasable programmable read only memory(EEPROM), flash memory, compact disk (CD) ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother non-transitory medium that can be used to carry or store desiredprogram code means in the form of instructions or data structures andthat can be accessed by a general-purpose or special-purpose computer,or a general-purpose or special-purpose processor. Also, any connectionis properly termed a computer-readable medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include CD, laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

As used herein, including in the claims, “or” as used in a list of items(e.g., a list of items prefaced by a phrase such as “at least one of” or“one or more of”) indicates an inclusive list such that, for example, alist of at least one of A, B, or C means A or B or C or AB or AC or BCor ABC (i.e., A and B and C). Also, as used herein, the phrase “basedon” shall not be construed as a reference to a closed set of conditions.For example, an exemplary step that is described as “based on conditionA” may be based on both a condition A and a condition B withoutdeparting from the scope of the present disclosure. In other words, asused herein, the phrase “based on” shall be construed in the same manneras the phrase “based at least in part on.”

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label, or othersubsequent reference label.

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “exemplary” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, well-known structures and devices are shownin block diagram form in order to avoid obscuring the concepts of thedescribed examples.

The description herein is provided to enable a person skilled in the artto make or use the disclosure. Various modifications to the disclosurewill be readily apparent to those skilled in the art, and the genericprinciples defined herein may be applied to other variations withoutdeparting from the scope of the disclosure. Thus, the disclosure is notlimited to the examples and designs described herein, but is to beaccorded the broadest scope consistent with the principles and novelfeatures disclosed herein.

1. A method for wireless communication at a user equipment (UE),comprising: receiving a synchronization signal block for a carrier, thesynchronization signal block associated with synchronization signalblock transmission attributes comprising a first subcarrier spacing(SCS); identifying one or more bandwidth part (BWP) transmissionattributes for transmissions within a BWP of the carrier, the one ormore BWP transmission attributes comprising a second SCS; determiningwhether a transmission over the BWP of the carrier is frequency divisionmultiplexed with the synchronization signal block based at least in parton the first SCS and the second SCS, wherein the transmission isfrequency division multiplexed if the first SCS is the same as thesecond SCS and the transmission is not frequency division multiplexed ifthe first SCS is different than the second SCS; and receiving thetransmission over the BWP of the carrier based at least in part ondetermining whether the transmission is frequency division multiplexedwith the synchronization signal block.
 2. The method of claim 1, whereinthe transmission comprises a downlink control channel transmission. 3.The method of claim 1, wherein the transmission comprises a downlinkshared channel transmission.
 4. The method of claim 1, wherein thesynchronization signal block transmission attributes comprise a beamidentifier of the synchronization signal block.
 5. The method of claim1, wherein the one or more BWP transmission attributes comprise atransmission beam direction or a reception beam direction.
 6. The methodof claim 1, wherein the one or more BWP transmission attributes areidentified based at least in part on a signal received from the carrier.7. The method of claim 1, wherein the first SCS is 120 kHz or 240 kHz.8. The method of claim 1, wherein the second SCS is 120 kHz.
 9. Themethod of claim 1, wherein the transmission comprises a downlink controlinformation transmission.
 10. The method of claim 1, wherein thetransmission is associated with remaining minimum system information.11. The method of claim 1, wherein the transmission is time divisionmultiplexed with the synchronization signal block if the first SCS isdifferent than the second SCS.
 12. The method of claim 1, furthercomprising: determining that a second transmission over the BWP of thecarrier is frequency division multiplexed with the synchronizationsignal block based at least in part on the first SCS being differentthan the second SCS; receiving the second transmission over the BWP ofthe carrier based at least in part on determining that the secondtransmission is frequency division multiplexed with synchronizationsignal block.
 13. The method of claim 12, wherein the secondtransmission comprises a downlink shared channel transmission.
 14. Themethod of claim 12, wherein the second transmission is associated withremaining minimum system information.
 15. The method of claim 12,wherein a guard band in the frequency domain is included between thesecond transmission and the synchronization signal block.
 16. Anapparatus for wireless communication at a user equipment (UE),comprising: a processor, memory in electronic communication with theprocessor; and instructions stored in the memory and executable by theprocessor to cause the apparatus to: receive a synchronization signalblock for a carrier, the synchronization signal block associated withsynchronization signal block transmission attributes comprising a firstsubcarrier spacing (SCS); identify one or more bandwidth part (BWP)transmission attributes for transmissions within a BWP of the carrier,the one or more BWP transmission attributes comprising a second SCS;determine whether a transmission over the BWP of the carrier isfrequency division multiplexed with the synchronization signal blockbased at least in part on the first SCS and the second SCS, wherein thetransmission is frequency division multiplexed if the first SCS is thesame as the second SCS and the transmission is not frequency divisionmultiplexed if the first SCS is different than the second SCS; andreceive the transmission over the BWP of the carrier based at least inpart on determining whether the transmission is frequency divisionmultiplexed with the synchronization signal block.
 17. The apparatus ofclaim 16, wherein the transmission comprises a downlink control channeltransmission or comprises a downlink shared channel transmission. 18.The apparatus of claim 16, wherein the synchronization signal blocktransmission attributes comprise a beam identifier of thesynchronization signal block.
 19. The apparatus of claim 16, wherein theone or more BWP transmission attributes comprise a transmission beamdirection or a reception beam direction.
 20. A non-transitorycomputer-readable medium storing code for wireless communication at auser equipment (UE), the code comprising instructions executable by aprocessor to: receive a synchronization signal block for a carrier, thesynchronization signal block associated with synchronization signalblock transmission attributes comprising a first subcarrier spacing(SCS); identify one or more bandwidth part (BWP) transmission attributesfor transmissions within a BWP of the carrier, the one or more BWPtransmission attributes comprising a second SCS; determine whether atransmission over the BWP of the carrier is frequency divisionmultiplexed with the synchronization signal block based at least in parton the first SCS and the second SCS, wherein the transmission isfrequency division multiplexed if the first SCS is the same as thesecond SCS and the transmission is not frequency division multiplexed ifthe first SCS is different than the second SCS; and receive thetransmission over the BWP of the carrier based at least in part ondetermining whether the transmission is frequency division multiplexedwith the synchronization signal block.